Google Git
Sign in
chromium / chromiumos / infra / dummies / general-sandbox / refs/heads/stabilize-10575.54.B
commite996a748f373f1941209c29126f541f1fe1adddd[log] [tgz]
authorPaul Hobbs <phobbs@google.com>Fri Nov 17 19:28:49 2017
committerchrome-bot <chrome-bot@chromium.org>Sat Nov 18 04:18:52 2017
tree6d2bd4fae126250084ebc48ffa273e6156c75c43
parent22a183b62a23572df437ddd8b21a3503ed97ce91 [diff]
Test CL for CL-exonerator rollout.

TEST=None
BUG=None

Change-Id: I915ce5db8aaf9c76c357986dab6c36e74677e648
Reviewed-on: https://chromium-review.googlesource.com/777539
Commit-Ready: Paul Hobbs <phobbs@google.com>
Tested-by: Paul Hobbs <phobbs@google.com>
Reviewed-by: Paul Hobbs <phobbs@google.com>
1 file changed
tree: 6d2bd4fae126250084ebc48ffa273e6156c75c43
  1. exonerator-test.txt
  2. 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.