commit | aac7ac16ec62af1b4e4c4fc40c72fd10dfed4c27 | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Mon Oct 04 19:29:09 2021 +0100 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue Oct 05 09:51:58 2021 +0100 |
tree | 2af9bff94e7789180b7689b16e54febd227e5365 | |
parent | 8a3948e9ae05f0053c9e85b653d43075129742de [diff] |
Adopt modern Jenkins terminology for the server The Jenkins terminology has been updated over a year ago (see [1]) and it is time to align our Jenkin server terminology to the new and more respectful term. [1] https://www.jenkins.io/blog/2020/06/18/terminology-update/ Change-Id: Ieb8cde25c695d0dbee1c18e9d72b36f41f6c5f3d
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/