<< Back to previous view |
[QB-1336] Do not release resources in upstream build even if it is waiting for completeness of downstream builds
|
|
Status: | Resolved |
Project: | QuickBuild |
Component/s: | None |
Affects Version/s: | 4.0.49 |
Fix Version/s: | 4.0.50 |
Type: | Improvement | Priority: | Major |
Reporter: | Robin Shen | Assigned To: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Remaining Estimate: | Unknown | Time Spent: | Unknown |
Original Estimate: | Unknown |
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. |