Release Engineering Project

1. Creating/Configuring/Verifying Jenkins Jobs

Clone and setup the repo:

git clone ssh://
cd releng
git review -s

Make changes:

git commit -sv
git review
remote: Resolving deltas: 100% (3/3)
remote: Processing changes: new: 1, refs: 1, done
remote: New Changes:
To ssh://
 * [new branch]      HEAD -> refs/publish/master

Test with tox:

tox -v -ejjb

Submit the change to gerrit:

git review -v

Follow the link to gerrit in a few moments the verify job will have completed and you will see Verified +1 jenkins-ci in the gerrit ui.

If the changes pass the verify job , the patch can be submitited by a committer.

Job Types

  • Verify Job
    • Trigger: recheck or reverify
  • Merge Job
    • Trigger: remerge
  • Experimental Job
    • Trigger: check-experimental

The verify and merge jobs are retriggerable in Gerrit by simply leaving a comment with one of the keywords listed above. This is useful in case you need to re-run one of those jobs in case if build issues or something changed with the environment.

The experimental jobs are not triggered automatically. You need to leave a comment with the keyword list above to trigger it manually. It is useful for trying out experimental features.

Note that, experimental jobs skip vote for verified status, which means it will reset the verified status to 0. If you want to keep the verified status, use recheck-experimental in commit message to trigger both verify and experimental jobs.

You can add below persons as reviewers to your patch in order to get it reviewed and submitted.

Or Add the group releng-contributors

Or just email a request for submission to

The Current merge and verify jobs for jenkins job builder can be found in releng-jobs.yaml.