This prioritizeBuilders function sorts builders by the length of their
associated worker lists, so that builders that can only be assigned to a
small number of workers are assigned to those workers before other
builds that don't have specific needs when resources are limited. An
example might be when a slot is available on an Ubuntu-based worker, and
"oe-selftest-ubuntu" and "genericx86-64" build requests exist in the
queue. Since oe-selftest-ubuntu requires an Ubuntu-based worker and
genericx86-64 does not, genericx86-64 will be assigned a higher value
(lower priority) so that oe-selftest-ubuntu is assigned to that worker
first.
[YOCTO #13644]
Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This means we get more commit information in the UI. It won't trigger
builds unless we configure it to. It also won't import any history,
just new commits while buildbot is running/polling.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Initial prototype of using yocto-autobuilder-helper scripts from vanilla
buildbot to replicate yocto-autobuilder configuration.
* README.md is updated to describe goals and approach
* TODO contains known issues and work items, TODO: comments in the code
point to specific locations of work
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
