commit | 1858b19d28c1ecf5f865079851d5e5ce2318c566 | [log] [tgz] |
---|---|---|
author | David Burger <dburger@chromium.org> | Fri Aug 16 14:49:53 2019 |
committer | David Burger <dburger@chromium.org> | Fri Aug 16 14:49:53 2019 |
tree | ba0f63d6f194c3e4308790757d5825027df4f6f4 | |
parent | b0930acdce24a98b4013b0b84ac9777faca65d93 [diff] |
Another trigger attempt for sample PUpr. TEST=None BUG=chromium:990858,chromium:990850 Change-Id: I4b1691e34058915631f538457edae7b207caf2aa
[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: