Remove UseBuildbucketScheduler. |
||||||||||
Issue descriptionWe should now be using buildbucket for all masters. It should be safe to remove UseBuildbucketScheduler, and the non-buildbucket logic.
,
Apr 19 2017
Related change.... chromeos_config_unittest 'testMasterBuildTypes' will be obsolete when we finish the buildbucket transition.
,
Apr 19 2017
we can't really remove the logic now. only chromiumOS/chromeOS/tryserver are configured with buildbucket, not all waterfalls.
,
Apr 19 2017
Yeah, but we should fix that. ;>
,
Apr 20 2017
I just went through all of our waterfalls. There are no master/slave groups that don't use buildbucket, except on the release waterfall. We need to update the release waterfall, to use buildbucket. However, if we remove this logic and force ourselves to always use buildbucket, release waterfall won't be affected until the next release branch which is roughly 6 weeks away.
,
May 16 2017
Who can do this work?
,
Jun 2 2017
,
Jun 12 2017
,
Jan 9 2018
,
Jan 9 2018
This should now be feasible.
,
Mar 19 2018
,
Apr 5 2018
,
Apr 5 2018
,
Jun 8 2018
,
Jul 27
Check if this is still needed.
,
Jul 27
Already fixed. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by dgarr...@chromium.org
, Apr 19 2017