| commit | bb663a9e62d9fb2ba343e08b06309166b32728ee | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Tue Oct 21 12:40:23 2025 +0200 |
| committer | Antonio Barone <syntonyze@gmail.com> | Tue Oct 21 13:27:41 2025 +0200 |
| tree | 70b4f92ebe4d19a1c0bce16e40ffb684c97ecb7b | |
| parent | d1d50275a01ee56acd4463f63d8aa36f2d3fc8d8 [diff] |
Allow GitHub plugin job to publish jar artifacts The GitHub plugin CI template ignored the extra-artifacts argument, so only the JSON metadata file was archived. As a result, github.jar and github-oauth.jar were built but not exposed as artifacts by CI. Change-Id: Ife7ac8b29b300a3b9f224d43a57ff3e7bb37830e
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 --require-hashes 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/