| << Back to previous view |
|
[QB-1075] Would like option to select nodes based on resource for inclusion in another resource
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 4.0.0 |
| Fix Version/s: | 9.0.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Don Ross | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
The new resource management is AWESOME! But I have a request.
My use case is as follows: I have different systems with different levels of power in the same resource, so I need to create a different Node Selection set for each one: - any build agent, 'BUILD_FARM_MEMBER' variable set, platform=Windows, processors=2: provide one resource - any build agent, 'BUILD_FARM_MEMBER' variable set, platform=Windows, processors=4: provide one resources - any build agent, 'BUILD_FARM_MEMBER' variable set, platform=Mac, processors=4: provide one resources - any build agent, 'BUILD_FARM_MEMBER' variable set, platform=Mac, processors=8: provide two resources I would find it cleaner if I could define one resource mapping to 'any build agent, 'BUILD_FARM_MEMBER' variable set', and then filter it again to identify the processors: - member of 'BUILD_FARM' resource, platform=Windows, processors=2: provide one resource - member of 'BUILD_FARM' resource, platform=Windows, processors=4: provide one resources - member of 'BUILD_FARM' resource, platform=Mac, processors=4: provide one resources - member of 'BUILD_FARM' resource, platform=Mac, processors=8: provide two resources That way, if the criteria for being a member of the build farm changes (which it just did today), or if I am using this as a template for a new set of resources I only have to change one entry. Also it would make the code easier to read. |