The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/manifest-internal/+/cae0b7e8848ad6588815120f828a265c51d1a7f4

commit cae0b7e8848ad6588815120f828a265c51d1a7f4
Author: Don Garrett <dgarrett@google.com>
Date: Thu Apr 05 17:38:17 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/manifest-internal/+/788ea34dc4dc040c96cf47e5a78d15d3408aa962

commit 788ea34dc4dc040c96cf47e5a78d15d3408aa962
Author: Don Garrett <dgarrett@google.com>
Date: Thu Apr 05 22:42:52 2018

The current gardener procedure doc to update.

http://doc/13zse2T7S-rMaFEvd0HhFvF95GWJWbuwY-QfeWUlOwbg

Steven mentioned that we need to make sure SoM still works. That might be an issue, and is worth investigating.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/964bf7d0e32b45b94b98be3f557450b0f957f852

commit 964bf7d0e32b45b94b98be3f557450b0f957f852
Author: Don Garrett <dgarrett@google.com>
Date: Fri Apr 06 21:44:25 2018

chromeos_config: Add two informationals to swarming.

Assign our currently active tot-chromium-pfq-informational builders to
the swarming waterfall. They are currently on the chromiumos.chromium
waterfall, but that was not recorded here. This change doesn't yet do
anything, but I plan to add LUCI scheduler entries for them shortly.

BUG= chromium:829169 
TEST=chromeos_config_unittest

Change-Id: I6d4b014b028be843406f5c4ed963aa9550a76a8c
Reviewed-on: https://chromium-review.googlesource.com/996953
Commit-Ready: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>

[modify] https://crrev.com/964bf7d0e32b45b94b98be3f557450b0f957f852/cbuildbot/config_dump.json
[modify] https://crrev.com/964bf7d0e32b45b94b98be3f557450b0f957f852/cbuildbot/waterfall_layout_dump.txt
[modify] https://crrev.com/964bf7d0e32b45b94b98be3f557450b0f957f852/lib/const/waterfall.py
[modify] https://crrev.com/964bf7d0e32b45b94b98be3f557450b0f957f852/cbuildbot/chromeos_config.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b690a8a742db6cb14594e1f1fe2f3039037c7531

commit b690a8a742db6cb14594e1f1fe2f3039037c7531
Author: chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Sat Apr 07 01:33:59 2018

Roll src/third_party/chromite/ c41a0f5ed..0f0cab3ea (3 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/c41a0f5eda5f..0f0cab3eae12

$ git log c41a0f5ed..0f0cab3ea --date=short --no-merges --format='%ad %ae %s'
2018-04-04 ihf chromeos_config: add bettyvirgl builder.
2018-04-04 dgarrett chromeos_config: Add two informationals to swarming.
2018-04-05 khmel arc: Mirror zipalign to ARC bucket.

Created with:
  roll-dep src/third_party/chromite
BUG= chromium:807873 , chromium:829169 


The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: Icae5a4e5edf06d06d465a123eb814b593ef0c0a3
Reviewed-on: https://chromium-review.googlesource.com/1000673
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#549009}
[modify] https://crrev.com/b690a8a742db6cb14594e1f1fe2f3039037c7531/DEPS

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/manifest-internal/+/e966114469a9a3d935449e114823b0e973dc84f1

commit e966114469a9a3d935449e114823b0e973dc84f1
Author: Don Garrett <dgarrett@google.com>
Date: Fri Apr 13 21:55:56 2018

I think I've prepared everything needed to move all chromiumos.chromium and all cbuildbot chromeos.chrome builders to swarming.

My intention is go to the Sheriff/Gardener handoff, and point them at the new UI "go/legoland-gardner".

Assuming no major issues pop up, I will land my existing CLs to remove builds from chromiumos.chromium, chromeos.chrome and force restarts. Then land the changes to add the new builds to the LUCI scheduler (to start the swarming builds). 

At that point, everything should be functional again, and I get to start cleaning up.

Destroy the beefy build slaves associated with chromeos.chrome, and land the CL to release their IPs, start the waterfall shutdown process with Infra Labs for chromiumos.chromium. chromium:833010 will track shutting down chromeos.chrome after it's final builder becomes unneeded.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/93752d3a7613e6ebcfeb14eaf5a9f8a78e569f95

commit 93752d3a7613e6ebcfeb14eaf5a9f8a78e569f95
Author: Don Garrett <dgarrett@google.com>
Date: Mon Apr 16 19:08:16 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/49284b8ad7f97c4e4c4b637dd82b185947c59cd6

commit 49284b8ad7f97c4e4c4b637dd82b185947c59cd6
Author: Don Garrett <dgarrett@google.com>
Date: Mon Apr 16 19:11:02 2018

master.chromiumos.chromium: Remove all builds.

This change removes all of the builds currently run on the
chromiumos.chromium waterfall, but does not delete the all of the
configuration information.

They have already been duplicated on LUCI swarming, which means the
builds here are redundant. This will be followed shortly by a request
to shutdown and remove the waterfall entirely.

BUG= chromium:829169 

Change-Id: I2c73fd9c9136995c4e3588a675c3db77559757fc
Reviewed-on: https://chromium-review.googlesource.com/1012862
Reviewed-by: Ningning Xia <nxia@chromium.org>
Commit-Queue: Don Garrett <dgarrett@chromium.org>

[modify] https://crrev.com/49284b8ad7f97c4e4c4b637dd82b185947c59cd6/masters/master.chromiumos.chromium/master_perf_cfg.py
[modify] https://crrev.com/49284b8ad7f97c4e4c4b637dd82b185947c59cd6/masters/master.chromiumos.chromium/master_goma_cfg.py
[modify] https://crrev.com/49284b8ad7f97c4e4c4b637dd82b185947c59cd6/masters/master.chromiumos.chromium/master_chromium_cfg.py
[modify] https://crrev.com/49284b8ad7f97c4e4c4b637dd82b185947c59cd6/masters/master.chromiumos.chromium/master_asan_cfg.py
[modify] https://crrev.com/49284b8ad7f97c4e4c4b637dd82b185947c59cd6/masters/master.chromiumos.chromium/slaves.cfg

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/manifest-internal/+/83e18687a265e2380c9858555eca3afe1e2b5270

commit 83e18687a265e2380c9858555eca3afe1e2b5270
Author: Don Garrett <dgarrett@google.com>
Date: Mon Apr 16 19:47:14 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/e355cf2569c0b254c78aef70641e06ce07d32ef4

commit e355cf2569c0b254c78aef70641e06ce07d32ef4
Author: Don Garrett <dgarrett@google.com>
Date: Mon Apr 16 23:16:28 2018

All builders have been migrated except for "chrome-tot-chromeos-amd64-generic".

This bug covers shutting down chromeos.chrome after that happens:
   https://crbug.com/833010 

This bug requests that chromiumos.chromium be recovered:
  https://crbug.com/833649


Nothing else left to do here!