commit | 9898b43a5c869e50e438d286f18b3399b7e51d79 | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Wed May 13 15:59:02 2020 +0100 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed May 13 15:59:02 2020 +0100 |
tree | e67b5e37d92529de9245a64a755176e39dfc1f51 | |
parent | ee0aca30d171bde77ae531bda793a544cb4eed8f [diff] |
gerritPipeline: do not reset labels when the build starts. Trivial rebase do not reset the Verified/Code-Style labels on changes. Gerrit CI should therefore respect the existing labels and not reset anything when a build starts. This allows changes to be merged immediately after a trivial rebase, without having to wait for another verification build. Issue: Issue 12721 Change-Id: I75a4964812ff2de0d0046c62dd455088eafaffb3
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/