New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 756649 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 848547
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 816564



Sign in to add a comment

Keep chromeos_config && luci-scheduler.cfg in sync?

Project Member Reported by dgarr...@chromium.org, Aug 17 2017

Issue description

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.
 
Owner: dgarr...@chromium.org
Status: Assigned (was: Untriaged)
Sounds like a task you filed for yourself? Is this cleanup? (Hotlist-Fixit candidate?)
Cc: nxia@chromium.org
Blocking: 816564
Mergedinto: 848547
Status: Duplicate (was: Assigned)

Sign in to add a comment