commit | e996a748f373f1941209c29126f541f1fe1adddd | [log] [tgz] |
---|---|---|
author | Paul Hobbs <phobbs@google.com> | Fri Nov 17 19:28:49 2017 |
committer | chrome-bot <chrome-bot@chromium.org> | Sat Nov 18 04:18:52 2017 |
tree | 6d2bd4fae126250084ebc48ffa273e6156c75c43 | |
parent | 22a183b62a23572df437ddd8b21a3503ed97ce91 [diff] |
Test CL for CL-exonerator rollout. TEST=None BUG=None Change-Id: I915ce5db8aaf9c76c357986dab6c36e74677e648 Reviewed-on: https://chromium-review.googlesource.com/777539 Commit-Ready: Paul Hobbs <phobbs@google.com> Tested-by: Paul Hobbs <phobbs@google.com> Reviewed-by: Paul Hobbs <phobbs@google.com>
[https://chromium.googlesource.com/chromiumos/infra/dummies/general-sandbox]
These repositories will not include any real code, but can be used to test or monitor aspects of the infrastructure.
For example, we may have some dummy repositories for:
New CQ features could be added behind a config flag, and rolled out to dummy repos first to minimize risk.
Pros:
Cons: