Google Git
Sign in
chromium / chromiumos / infra / dummies / general-sandbox / a790032d72fefdb8eccb41ad591fccb65bbdf971
commita790032d72fefdb8eccb41ad591fccb65bbdf971[log] [tgz]
authorAviv Keshet <akeshet@chromium.org>Wed Apr 18 17:03:15 2018
committerAviv Keshet <akeshet@chromium.org>Wed Apr 18 17:03:15 2018
tree051690281a14f2751bd89d24088946b231bfe81a
parente996a748f373f1941209c29126f541f1fe1adddd [diff]
foo: a no-op commit

BUG=None
TEST=None

Change-Id: I497a4e9db593c8120c5f56deee373e89b957fc4f
1 file changed
tree: 051690281a14f2751bd89d24088946b231bfe81a
  1. exonerator-test.txt
  2. foo
  3. README.md
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.