commit | bf7ed02d90a4c9943ba76ba4e5276ea7e761619f | [log] [tgz] |
---|---|---|
author | Thomas Draebing <thomas.draebing@sap.com> | Mon Oct 14 08:59:58 2019 +0200 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed Oct 16 23:13:39 2019 +0000 |
tree | 909c294edb1f5865531eade8be5715eca06956e9 | |
parent | de54f73411116a8dd7d2cddda728d7d8fb302f79 [diff] |
Add multibranch pipeline to validate the gerrit project This change adds a multibranch pipeline that will verify all changes of Gerrit that contain a Jenkinsfile in their working tree. It has the same task as the Gerrit-verifier-flow job, which uses the deprecated workflow job type. The old job can be removed as soon as all branches that are supposed to be verified have a Jenkinsfile. Change-Id: I5942ddfb73e83ad85ec527d2edd6601e35ddbf7a
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/