commit	539ad9639b850d22431131691db79352d2f1b5b1	[log] [tgz]
author	Andrii Shyshkalov <tandrii@chromium.org>	Mon Jun 06 16:19:40 2016
committer	Andrii Shyshkalov <tandrii@chromium.org>	Mon Jun 06 16:19:40 2016
tree	7386fcb87130479bc0cca61ba9cffad588c232c8
parent	a6103fe68d1fb2d59657a4cf7b3d07423dd7aba0 [diff]

tree: 7386fcb87130479bc0cca61ba9cffad588c232c8

README.md

Simple CI with Gerrit and CQ

https://goto.google.com/chrome-simple-ci

Steps so far:

Create new repository in Gerrit, but you already have it, don't you?
Register it in luci-config - ask infra. Example: https://chrome-internal-review.googlesource.com/#/c/262666/

(Public repos only) Mark your repo as such:

 git checkout --orphan infra/config
 wget https://chromium.googlesource.com/infra/infra.git/+/infra/config/project.cfg
 git add project.cfg && git commit -m "Mark this repo public"
 git push origin infra/config
 git checkout master  # Go back to familiar branch.

Get basic setup for your Gerrit codereview patches auto-tested:

 git checkout master
 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.

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.