| commit | 8bb2ba9c6560a92176aceee0614d4d07576f8b14 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Wed Jul 15 14:25:11 2020 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed Jul 15 13:50:23 2020 +0000 |
| tree | ce0eb61dae7b2daf3a10cfa7524b35715878d094 | |
| parent | 0dead1760538b1583bfdab65409e46b30a16be70 [diff] |
Always run PolyGerrit lint on merge commits Merge commits may pull in changes that are not explicitly listed as part of the merge but are coming from earlier branches and did not cause any conflict. Always run PolyGerrit lint when a merge commit is detected, as the process is not part of the critical path of the build and it would make sure that no un-checked code is pulled when the merge commit is submitted. Bug: Issue 13143 Change-Id: Icd126693b39d113139fac7070c9fe92603be76bd
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/