| << Back to previous view |
|
[QB-722] Separate configuration enable/disable from sequential/concurrent run mode
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 3.0.17 |
| Fix Version/s: | 4.0.0-M2, 4.0.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Robin Shen | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 2 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
From customer,
Without a lot of history, here is what appears to cause a problem. We have many dependent builds. Most of these builds are set to run mode of DISABLED as they are triggered in groups through dependency checking. Due to a misconfiguration, several of these tiggering builds were set to run mode CONCURRENT. All of our builds assume an isolated workspace, and so CONCURRENT is clearly wrong. However, it appears that this run mode is being "inherited" by the DISABLED builds when they are triggered from a CONCURRENT build. Before we changed the triggering builds to SEQUENTIAL we noticed all of our builds running CONCURRENT. It seems that since the concurrent build capability of a build should apply even when DISABLED, that it should be its own property. |
| Comments |
| Comment by Roger Perkins [ 02/Nov/10 01:59 PM ] |
| This would also be useful for us as I could then set "disable" at a high node and disable all child nodes easily through inheritance, where currently this isn't possible as the high nodes are set to stop them being used to try and initiate a build at that level. It would mean you could copy a hierachy of nodes and set "disable" to stop child configurations triggering before you have a chance to change them |