Google Git
Sign in
chromium / playground / gerrit-cq / normal / 2e82a4a302eb42df3ad359f5bdc73b4c62addfd5
commit2e82a4a302eb42df3ad359f5bdc73b4c62addfd5[log] [tgz]
authorAndrii Shyshkalov <tandrii@chromium.org>Fri Jun 09 13:03:43 2017
committerCommit Bot <commit-bot@chromium.org>Fri Jun 09 13:04:56 2017
tree59d206cadcf838f3c750c6aa8450fa6cab381cda
parenta7dd09f9edded18480e7d2ce1e8f32f104a14818 [diff]
Test CQ traffic splitting: default 50% w/o whitelist.

Bug: 660385
Change-Id: I93109d95074379f0ed89801280ed43e2e37a7f45
No-Try: True
No-Presubmit: True
Reviewed-on: https://chromium-review.googlesource.com/529304
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
1 file changed
tree: 59d206cadcf838f3c750c6aa8450fa6cab381cda
  1. infra/
  2. codereview.settings
  3. README.md
  4. test.cpp
  5. test1.py
  6. test2.py
  7. whitespace.txt
README.md

Normal CQ workflow.

First make sure you have proper codereview.settings like the one in this repo.

Committers set the CQ label to either 1 (Dry run) or 2 (Ready for CQ) which will automatically submit change after all conditions are met:

  • CQ verifiers pass the change.
  • Gerrit allows to submit it.

Clone it this normal way:

git clone https://chromium.googlesource.com/playground/gerrit-cq/normal

Initialize your repository first:

git new-branch feature
# hack, hack, hack
git add changed.file
git commit
# You can hack more, and commit again,
# but they'll all be squashed by default in git cl upload step.

# OK, now ask others for review:
git cl upload

# Make changes locally per review.
git add changed.file
git commit

# Now upload new patchset.
git cl upload