commit | 8eb62fe8106581b173f92eeff7b0568ef06a2e5f | [log] [tgz] |
---|---|---|
author | Thomas Draebing <thomas.draebing@sap.com> | Wed Oct 09 16:41:40 2019 +0200 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu Oct 10 12:43:35 2019 +0000 |
tree | 167a9723de9dc18c2bd34080e459105506f298b1 | |
parent | d9cd0d9c42aec8201d314116ee70fe489ec61add [diff] |
Add job that triggers GerritCodeReview-pipelines Jobs that were implementing a multi branch pipeline with the GerritCodeReview-plugin were not triggered automatically, since the Gerrit trigger plugin cannot be used with gerrit.googlesource.com. This change adds a pipeline that regularly triggers all jobs of this type registered with it. Change-Id: I7803cc37e169a23adced2619546a1af3161ce74b
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/