| Key: |
QB-1336
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Robin Shen
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 10/Aug/12 12:56 PM
Updated: 10/Aug/12 01:22 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
4.0.49
|
| Fix Version/s: |
4.0.50
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
This can avoid the situation where multiple builds can run even if resource is exhausted when they trigger and wait for the same build. However this can result in deadlock if upstream and downstream builds are requesting the same resource. There are two approaches to avoid the deadlock:
1. Do not wait for completeness of another build. For QuickBuild repository, this means not to choose the "latest (trigger new if necessary) option".
2. If one build has to wait for completeness of another build, make sure these two builds do not requesting the same set of resource.
|
|
Description
|
This can avoid the situation where multiple builds can run even if resource is exhausted when they trigger and wait for the same build. However this can result in deadlock if upstream and downstream builds are requesting the same resource. There are two approaches to avoid the deadlock:
1. Do not wait for completeness of another build. For QuickBuild repository, this means not to choose the "latest (trigger new if necessary) option".
2. If one build has to wait for completeness of another build, make sure these two builds do not requesting the same set of resource. |
Show » |
| There are no comments yet on this issue.
|
|
Do not release resources in upstream build even if it is waiting for completeness of downstream builds