Currently, we define our build configurations in chromeos_config.py, and it defines the waterfall that builders are expected to run on. Builder scheduling is then controlled by buildbot.
We have logic in some buildbot waterfalls to read the chromeos build config, and then do thing "right thing" scheduler wise automatically (other than needing a waterfall restart).
As we switch from buildbot scheduling to luci-scheduling, our our scheduler configuration no longer reads from chromeos_config.py (directly or indirectly).
Instead of manually editing luci-scheduler.cfg (chromite -b infra/config) for each new builder, it would be nice to have some automatic system to make sure the build configuration and scheduler stay in sync with each other.
PS: Each new builder means all non-slave builders (masters, incrementals, etc), otherwise this would be unsustainable.
Comment 1 by pprabhu@chromium.org
, Aug 21 2017Status: Assigned (was: Untriaged)