Build Gerrit branches automatically

The Gerrit-verifier-pipeline is now responsible to
build only the changes that are discovered by the
Checks API. The stable branches need a different way
to get triggered: use the standard pollscm configuration
to make sure that they are checked and rebuilt.

Change-Id: Ieb07c8428291a59d224a8fa3afc7bd50872ed4c9
1 file changed
tree: 36efb200c2d5ddc5c8c0c31d8e28468d05267369
  1. jenkins/
  2. jenkins-docker/
  3. worker/
  4. .gitignore
  5. Jenkinsfile
  6. README.md
  7. yamllint-config.yaml
README.md

Gerrit CI scripts

Providing jobs

This project uses Jenkins Jobs Builder [1] to generate jobs from yaml descriptor files.

To add new jobs reuse existing templates, defaults etc. as much as possible. E.g. adding a job to build an additional branch of a project may be as easy as adding the name of the branch to an existing project.

To ensure well readable yaml-files, use yamllint [2] to lint the yaml-files. Yamllint can be downloaded using Python Pip:

pip3 install yamllint

To run the linter, execute this command from the project's root directory:

yamllint -c yamllint-config.yaml jenkins/**/*.yaml

Yamllint will not fix detected issues itself.

[1] https://docs.openstack.org/infra/jenkins-job-builder/index.html [2] https://pypi.org/project/yamllint/