| commit | a5bb7a83625b81549577314dbad03ff1ac310ea1 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 28 13:04:12 2020 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 28 13:04:12 2020 +0100 |
| tree | 7594c23095fe3df6d5b8e896fb7e334b4f2068a3 | |
| parent | a19af81c1ed4c7eea74e1bcc91f94c1fbeab2244 [diff] |
Do not find plugins JARS in bazel-bin subdirectories
Fix the detection of the plugin's target jar by explicitly
looking in bazel-bin/plugins/{name}/{name}.jar.
If the plugin had somewhere in its nested structure another {name}.jar
file generated (e.g. checks tests) it would have confused the collection
of the resulting artifact and archived the tests instead of the plugin
jar file.
Bug: Issue 12817
Change-Id: I5afc801aa630d3040371f104ca92cd2b415e6913
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/