| commit | 92e10d3a0af06e74145300ac1f24c7440ffd1fc2 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Mon Feb 10 07:47:56 2020 +0000 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed Jun 17 23:40:38 2020 +0000 |
| tree | b76d3b30613ab9274503c2adc98205fb2f2074ed | |
| parent | fe195465f1685da4ffe81d21f4c0d6ea5c58e47a [diff] |
Do not limit the maximum number of jobs The maximum number of verification jobs must not be limited in number but only in time, otherwise the verification pipeline would stop when there are too many open changes. This is due to how the Checks integration and API works: once a change is scheduled for being built is automatically not returned anymore as pending, causing the job to be considered as removed. If there are too many open changes and thus too many removed jobs, the build just started would risk to be immediately removed because of the automatic mechanism of discarding old builds. By removing the limit, prevent that situation to happen. It will still remove the old builds by time and not by number of builds anymore. Change-Id: I68d0b65e015be376420f83ef2ac57373bdb0d44a
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/