Google Git
Sign in
chromium / chromiumos / infra / dummies / general-sandbox / refs/heads/stabilize-12371.11.B
commit88ef977562c7172763ca413a8e74ae9318fb2dd0[log] [tgz]
authorChris McDonald <cjmcdonald@chromium.org>Wed Jun 19 19:40:18 2019
committerChris McDonald <cjmcdonald@chromium.org>Wed Jun 19 19:40:18 2019
treed6c2babc1ee349f7966c57094c4f3e977e3b8f04
parent23d1a3f86f7da550100b97f9897a258d3ac70834 [diff]
Revert "TESTING: set myself as OWNER for dummy repo"

This reverts commit 23d1a3f86f7da550100b97f9897a258d3ac70834.

Reason for revert: Done with test

Original change's description:
> TESTING: set myself as OWNER for dummy repo
> 
> BUG=None
> TEST=None
> 
> Change-Id: Ia0d510a02ba2572a13022d7e689106d194e853f1

Bug: None
Change-Id: Ia0d448b643cb7bec66a1a64a1d56986f5ea35a17
1 file changed
tree: d6c2babc1ee349f7966c57094c4f3e977e3b8f04
  1. atest-test.txt
  2. exonerator-test.txt
  3. foo
  4. 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.