Issue 794675  has been merged into this issue.

Mike started this. I'm going to rename it to staging, and make it accessable from "cros tryjob".

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

commit 992b32153c6edbc421424b0356a2c4bb7dfc6688
Author: Don Garrett <dgarrett@google.com>
Date: Thu Jun 28 20:24:06 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/e265532c8b5bf0d6aae6f06cc8b36382e2139aa6

commit e265532c8b5bf0d6aae6f06cc8b36382e2139aa6
Author: Don Garrett <dgarrett@google.com>
Date: Thu Jun 28 20:25:01 2018

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

commit 0195e8701a7f0940e2611b7cf9a86541a1934349
Author: Don Garrett <dgarrett@google.com>
Date: Fri Jun 29 08:08:57 2018

cros tryjob: Add --staging to run against test builder.

We have a LUCI builder named "Staging" to allow testing of changes to
the build environment itself. This CL adds --staging as an alternative
to --remote for cros tryjobs. Builds run that way will be run against
the new environment.

BUG= chromium:765749 
TEST=run_tests + cros tryjob --staging success-build

Change-Id: I18556eac06cb2e9a4a046c84b95d5e7315ab2856
Reviewed-on: https://chromium-review.googlesource.com/1119110
Commit-Ready: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Mike Nichols <mikenichols@chromium.org>

[modify] https://crrev.com/0195e8701a7f0940e2611b7cf9a86541a1934349/cli/cros/cros_tryjob_unittest.py
[modify] https://crrev.com/0195e8701a7f0940e2611b7cf9a86541a1934349/lib/config_lib.py
[modify] https://crrev.com/0195e8701a7f0940e2611b7cf9a86541a1934349/cli/cros/cros_tryjob.py

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

commit 3f7d4aa958223a9efc9cc0a1d05d0b24078823d7
Author: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Fri Jun 29 16:00:18 2018

Roll src/third_party/chromite 525fc9fdb588..7869e579e31e (4 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/525fc9fdb588..7869e579e31e


git log 525fc9fdb588..7869e579e31e --date=short --no-merges --format='%ad %ae %s'
2018-06-29 vapier@chromium.org lint: handle indentation of section subtext
2018-06-29 vapier@chromium.org lint: clean up bad docstring indentation
2018-06-29 mikenichols@chromium.org [portage_util] Additional logging for portage_util to capture commit id.
2018-06-29 dgarrett@google.com cros tryjob: Add --staging to run against test builder.


Created with:
  gclient setdep -r src/third_party/chromite@7869e579e31e

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.



BUG=chromium:485005,chromium:None,chromium:854633,chromium:765749
TBR=chrome-os-gardeners@chromium.org

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