| << Back to previous view |
|
[QB-1613] Addition of logical resources
|
|
| Status: | Open |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.0.7 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Keni Popovski | Assigned To: | Robin Shen |
| Resolution: | Unresolved | Votes: | 1 |
| Remaining Estimate: | 5 days | Time Spent: | Unknown |
| Original Estimate: | 5 days | ||
| Environment: | Ubuntu, also Windows 7 | ||
| Description |
|
Currently QuickBuild has the notion of Resources, although these are directly linked to nodes. It appears the linkage is there to allow a configuration to select a node based upon the various selection criteria it has.
Unfortunately, there are times when a logical resources is required, one which is not linked to a node. Consider the case where a configuration must run on a particular node (e.g. due to OS requirements), but it also needs to utilize another set of hardware. If this particular hardware is tied directly to another (single) node, then the node selection criteria can never be satisfied as there are no commonalities. In this case, a logical resource is required, one which doesn't contribute to the node selection, but rather acts as a simple reservation marker. If the marker is taken, the configuration cannot run, and hence must be queued. |
| Comments |
| Comment by Robin Shen [ 01/May/13 01:17 AM ] |
| In this case, how about declaring requirement for another hardware in a child step? |
| Comment by AlSt [ 13/May/13 03:08 PM ] |
|
That's exactly the thing I would like to have in QB. Working with child steps is in my opinion not a satisfying solution, because it is 'too late' - builds are already running, when they are able to check if a resource is available...
|