Readme + minor fixes.
Change-Id: I7984807492d85a2b44936dea5e8e9d842717fedd
diff --git a/README.md b/README.md
index 94ee1ff..0807391 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
# Simple CI with Gerrit and CQ
-See https://goto.google.com/chrome-simple-ci
+https://goto.google.com/chrome-simple-ci
Steps so far:
@@ -18,8 +18,23 @@
git push origin infra/config
git checkout master # Go back to familiar branch.
-2. Copy-paste and edit the following files from this repo:
+2. Get basic setup for your Gerrit codereview patches auto-tested:
git checkout master
- wget infra/config/cq.cfg
- infra/config/ci.cfg
+ mkdir infra/config && cd infra/config
+ wget https://chromium.googlesource.com/playground/gerrit-cq/simple-ci/+/master/infra/config/ci.cfg
+ wget https://chromium.googlesource.com/playground/gerrit-cq/simple-ci/+/master/infra/config/cq.cfg
+
+ Now customize `cq.cfg` and `ci.cfg`, and land the change.
+
+ *Note: it takes up to 40 minutes for this change to become active.* So, do
+ next step while you are waiting.
+
+
+3. Ask your Gerrit admin to:
+
+ 1. grant `chrome-commit-bot` group `-1..+1` voting rights on `refs/heads/master`
+ 2. add a label `Commit-Queue` `0..1` on `refs/heads/master`. Setting default
+ value `1` will trigger tests automatically on patch upload. Otherwise,
+ developers will have to set it manually to `1`, so grant them rights to
+ do so.
diff --git a/infra/config/ci.cfg b/infra/config/ci.cfg
index 0349c5f..aba0b22 100644
--- a/infra/config/ci.cfg
+++ b/infra/config/ci.cfg
@@ -1,6 +1,8 @@
# Each line must be a valid standalone command to run.
# DO NOT RELY ON THE ORDER, they could be executed in random order and even on
# different machines.
+
+# TODO(you): modify these to suit your needs.
./test2
python test1.py ok
python test1.py bad
