Google Git
Sign in
chromium / chromiumos / infra / dummies / general-sandbox / bd003ff79ea796e84cbbd498670c40748bf97f98
commitbd003ff79ea796e84cbbd498670c40748bf97f98[log] [tgz]
authorEvan Hernandez <evanhernandez@chromium.org>Wed Aug 21 19:22:48 2019
committerEvan Hernandez <evanhernandez@chromium.org>Wed Aug 21 19:23:28 2019
treef56741f302bad46b77fce2b4e05c5e930baaca22
parent2bbc4e4e115f0421cd9def87c7a0dfa1fc1e32bc [diff]
another trigger

Change-Id: Ibb176a11b4dd4c0b314928cd623ded792aabce9d
1 file changed
tree: f56741f302bad46b77fce2b4e05c5e930baaca22
  1. atest-test.txt
  2. exonerator-test.txt
  3. foo
  4. README.md
  5. trigger
README.md

General sandbox repo

[https://chromium.googlesource.com/chromiumos/infra/dummies/general-sandbox]

Motivation

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:

  • Testing git merge handling in the CQ
  • New CQ submission / rejection / exoneration behaviors
  • Blackbox monitoring of pre-cq or cq submission

New CQ features could be added behind a config flag, and rolled out to dummy repos first to minimize risk.

Pros:

  • Easily accomplished.
  • Allows for safer rollouts of new CQ features.

Cons:

  • Encourages testing in production. (rebuttal: we already test a lot in production due to lack of a staging environment that replicates the real CQ environment; this just makes such inevitable tests safer).
  • Adds some junk repos to the manifest.