commit | a19af81c1ed4c7eea74e1bcc91f94c1fbeab2244 | [log] [tgz] |
---|---|---|
author | David Ostrovsky <david@ostrovsky.org> | Fri May 22 16:44:17 2020 +0200 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue May 26 16:22:57 2020 +0000 |
tree | 542326e3c6eac91e7a34b2b9ab85deaefc87b62a | |
parent | e6a5cc86ce4aeeacb083a08cf19faeb8d827e5f4 [diff] |
Avoid boilerplate in no tests found use case As suggested in this upstream issue: [1] use always pass test to avoid Bazel returning exit code 4 and corresponding boilerplate in no tests found use case. [1] https://github.com/bazelbuild/bazel/issues/11465 Change-Id: I3b102d0efae69cf975e0e2787537efc5898d5938
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/