commit | 8a3948e9ae05f0053c9e85b653d43075129742de | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Mon Oct 04 19:21:48 2021 +0100 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue Oct 05 08:48:50 2021 +0000 |
tree | 37ea07edab30437dab35f5a13d8439f8250a377a | |
parent | bf90196b523162df9833b00379af3b38643175af [diff] |
Adopt modern Jenkins terminology for build agents The Jenkins terminology has been updated over a year ago (see [1]) and it is time to align all our images and builds to the new and more respectful term of agent to refer to build workers. [1] https://www.jenkins.io/blog/2020/06/18/terminology-update/ Change-Id: I8e9246f6d06d2a93d5ab612843fc41b41e47ccf3
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/