| commit | 0daa6d67345572d497fa3f84fc21319f79e6756e | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Wed Jun 17 09:16:53 2020 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed Jun 17 08:56:19 2020 +0000 |
| tree | 55932cbeb884615b31f38e98337824043f66aa38 | |
| parent | 058bcda89b3131a4bbccac7f6099b244bc4fae0f [diff] |
Move credentials-id at SCM/origin level Even though Jenkins Job Builder supports the credentials-id at both SCM and Source level, it would ignore the ones at SCM level if there is a "sources" array defined. Unfortunately that isn't detected by the Jenkins Job Builder at all and just results in the configuration of SCM sources without any credentials-id, which would result in a broken job definition. Move all the credentials-id definition at source level, when present, so that the credentials are set as expected in all jobs definition. TODO: Jenkins job builder needs fixing in both documentation and implementation. Change-Id: Ia10bcb4a6a8bdd5962450669ac567c7d1625b884
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/