| commit | 494cb71844e8cb001269ca7a6afeb17d1ef94a5a | [log] [tgz] |
|---|---|---|
| author | Andrii Shyshkalov <tandrii@chromium.org> | Wed Jun 08 21:12:25 2016 |
| committer | Andrii Shyshkalov <tandrii@chromium.org> | Wed Jun 08 21:12:25 2016 |
| tree | 47e02b506694f15fcdcf8d11539e2841267dc135 | |
| parent | 255f3eda4b177ab222644512939f2ed03997e193 [diff] |
Good CL. BUG= Change-Id: I417d309372632ae3ae48639762063bf37f5ff000
https://goto.google.com/chrome-simple-ci
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:
chrome-commit-bot group -1..+1 voting rights on refs/heads/masterCommit-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.Point your Gerrit admin to this example: https://chromium.googlesource.com/playground/gerrit-cq/simple-ci/+/refs/meta/config