commit | f8db6bf05f5003a0c828c42738144703adf32279 | [log] [tgz] |
---|---|---|
author | David Burger <dburger@chromium.org> | Fri Aug 16 15:07:32 2019 |
committer | David Burger <dburger@chromium.org> | Fri Aug 16 15:08:44 2019 |
tree | 76c5cd1c084e9855aaf9d538d3fb461eb514baff | |
parent | 1858b19d28c1ecf5f865079851d5e5ce2318c566 [diff] |
Another trigger change to trigger sample PUpr testing. TEST=None BUG=chromium:990858,chromium:990850 Change-Id: I8febd1fc7f24e84c4bbfb9587055b92c1b4addf3
[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: