Clone this repo:
  1. bbe0441 Add gerrit_cq_ability verifier. by Andrii Shyshkalov · 7 months ago master
  2. 9a29d84 Correction. by Andrii Shyshkalov · 1 year, 3 months ago
  3. cf19534 More. by Andrii Shyshkalov · 1 year, 3 months ago
  4. a842433 Update doc. by Andrii Shyshkalov · 1 year, 3 months ago
  5. 494cb71 Good CL. by Andrii Shyshkalov · 1 year, 3 months ago

Simple CI with Gerrit and CQ

Example CLs:

How do I get this?

Contact tandrii@{,} first, though the rest of steps should be doable without his involvement.

  1. Create new repository in Gerrit, but you already have it, don't you?

  2. Register it in luci-config - ask infra. Example:

  3. (Public repos only) Mark your repo as such:

     git checkout --orphan infra/config
     git add project.cfg && git commit -m "Mark this repo public"
     git push origin infra/config
     git checkout master  # Go back to familiar branch.
  4. Get basic setup for your Gerrit codereview patches auto-tested:

     git checkout master
     mkdir infra/config && cd infra/config

    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.

  5. Ask your Gerrit admin to:

    1. On the Gerrit host itself, make sure CQ bot account exists, and has a corresponding group. Then use that group in the following step. Note, adding bot account is non-trivial, see (internal only, sorry) http://go/gob-docs.

    2. On the project itself:

      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

      Point your Gerrit admin to this example:

    3. (If your repo is private, and you will use our machines to actually run tests) We need to make sure our bots can access your repository. For it's already done, but for other hosts, contact chrome-infra@.

  6. Upload your next CL and vote on Commit-Queue label +1.