| commit | 93c5b559bfaaf51da9bd0e71e35480c7697c1e9b | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Thu Nov 28 16:48:32 2024 +0100 |
| committer | Antonio Barone <syntonyze@gmail.com> | Fri Nov 29 09:26:28 2024 +0000 |
| tree | 6669b43f56db5a1ed110fc4f6bd7f07bfd13ce5d | |
| parent | c4b43999f878ba9de344d9f89c670491c61efeee [diff] |
Build plugins on java21 when Gerrit is on stable-3.11 Change I5572a18a introduced the ability of building plugins on java21, when their building branch was stable-3.11. However, plugins that were building different branches ogainst gerrit stable-3.11 were just built on default java version (java 17). For example the javamelody plugin that builds its master branch against multiple Gerrit versions, was always building using java17, even when the gerrit version was stable-3.11. Change-Id: I823d3fe781f149c9fc353862309d553dcdf0b41c
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/