Elaborate build slave assignments for loops
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linaro-ci-dashboard |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
As a quick measure to make builds run properly on demo server setup, a simple build slave assignments was implemented, where each job created in Jenkins has loop classname as a label, and then Jenkins global config assigns that to specific build slaves/master.
This needs to be elaborated in the following directions:
1. There're loop types which require different slave types based on their properties (but otherwise static mapping), e.g. public vs private android builds. For this case proposed solution was to split this loop in 2 types, because it's really access-control related.
2. Some loops may want to let user select a slave type to use, from a predefined repertoire for that loop type.
3. Loop types and slave labels should be ideally decoupled.
Marking as "Won't fix" since the development of this project is on-hold ATM.