Move to buildbucket scheduling for as many ChromeOS builds as possible. |
|||||
Issue descriptionWe currently use buildbot scheduling for many of our builders, which makes them invisible to new UI efforts that are based on buildbucket. Further, before we can move to swarming, we need to replace all buildbot scheduling logic. Since we can use buildbucket to schedule both buildbot and swarming builds, we should start the scheduling change now.
,
Aug 17 2017
ChromeOS waterfall: # Continuous master-paladin pre-cq-launcher # 5 minute intervals chell-incremental lakitu-incremental link-depthcharge-full-firmware # Fixed schedule master-release # 2 AM, 10 AM, 6 PM master-toolchain # 7 AM master-android-pfq # Every 3 hours master-nyc-android-pfq # Every 3 hours # Triggered by new Chrome versions, currently git-triggered master-chromium-pfq
,
Aug 17 2017
ChromiumOS waterfall: All of these builders are currently being triggered any ChromeOS submission. This is effectively a continuous build. # 5 minute intervals amd64-generic-incremental daisy-incremenal amd64-generic-full arm-generic-full daisy-full lakitu-full oak-full amd64-generic-asan chromiumos-sdk
,
Aug 17 2017
ChromeOS Release waterfall: Based on code inspection, I have no idea how these work. reef-android-nyc-pre-flight-branch release-R61-9765.B samus-chrome-pre-flight-branch release-R61-9765.B veyron_tiger-android-mnc-pre-flight-branch release-R61-9765.B master-release release-R61-9765.B cyan-android-mnc-pre-flight-branch release-R60-9592.B reef-android-nyc-pre-flight-branch release-R60-9592.B samus-chrome-pre-flight-branch release-R60-9592.B master-release release-R60-9592.B samus-pre-flight-branch release-R59-9460.B master-release release-R59-9460.B
,
Sep 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/3e896acecd50171aa637a8d7e08f2ffe80db6a0c commit 3e896acecd50171aa637a8d7e08f2ffe80db6a0c Author: Don Garrett <dgarrett@google.com> Date: Fri Sep 01 18:35:49 2017 infra/config: All most chromeos builders. Add schedulers for all chromeos waterfall builders that need them, other than master-chromium-pfq, which requires git triggering. BUG= chromium:751272 TEST=None Change-Id: Ib13876f369e6a058989ec71b67b84a4fbc78a569 Reviewed-on: https://chromium-review.googlesource.com/620067 Reviewed-by: Ningning Xia <nxia@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> [modify] https://crrev.com/3e896acecd50171aa637a8d7e08f2ffe80db6a0c/luci-scheduler.cfg
,
Sep 1 2017
The new schedulers for the chromeos waterfall are in-place and paused. I'll start turning off the buildbot schedulers now.
,
Sep 1 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/tools/build/+/42c61b26a3c84c10b7736b083ec71be3753111b5 commit 42c61b26a3c84c10b7736b083ec71be3753111b5 Author: Don Garrett <dgarrett@google.com> Date: Fri Sep 01 23:10:10 2017
,
Sep 13 2017
,
Oct 30 2017
,
Oct 30 2017
,
Feb 20 2018
This is in place for every master/slave group, and for enough other builders to prove out the scheduling mechanism. Other builders will be converted as they move to swarming. Declaring success. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bugdroid1@chromium.org
, Aug 2 2017