commit | 9184fab404f43e94b3604da4f0f97151ec66749e | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Sun Mar 24 11:24:57 2024 +0000 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu Mar 28 18:36:23 2024 +0000 |
tree | ccafc79cc5d528d89709269cd29d215ae4926e67 | |
parent | 00cc598e8bb94d11ecd25747804e4df9dfbf0864 [diff] |
Stop building modules continuously The modules Job definition includes two origins, which makes the Jenkins SCM polling very confused on whether the job has new commit or not. Use always the 'origin/' prefix so that Jenkins knows that the build needs to be triggered only when the libModule has new commits. Change-Id: I839c9b543bb08f646dc2d10d5ed0e0bc93596e15
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 --require-hashes 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/