commit | 7a701f41769a55fe8288f4f8e55d2a025bb6642b | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Sun May 17 22:25:29 2020 +0100 |
committer | David Pursehouse <dpursehouse@digital.ai> | Tue May 19 03:46:09 2020 +0000 |
tree | fc948156f6091a382f0143a48c7c5ef4030851a3 | |
parent | cfc311b480d486734bfd68f50cc44c67eebed491 [diff] |
Run all documentation tests after PolyGerrit build Gerrit on stable-2.16 does not have any Documentation/... tests and therefore should be accepted also with exit code 4. Other branches may have Documentation/... tests and therefore should be considered valid with exit code 0. Accept both 4 and 0 as a successful execution codes and fail the build if Documentation/... tests exited with a different vaue. Change-Id: I83f4aa3794965f090edef8b41c12e6da39497bdc
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/