| commit | 5c07e7bc1086e03b43fc5605b78cf855e8585fea | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Fri Sep 26 16:17:03 2025 +0200 |
| committer | Antonio Barone <syntonyze@gmail.com> | Tue Sep 30 02:10:33 2025 -0700 |
| tree | a7c885eea18febcf4bfddfdebe231d63c0ff0801 | |
| parent | bcba8acf2bc15023dac04ee397b44fa96ecb35bc [diff] |
Add release agent template to internal Jenkins This change registers the `gerrit-release-bazel` Docker image as a Jenkins agent template in the internal server configuration. By adding this agent, the Jenkins cluster can provision containers dedicated to running the Gerrit release process. This lays the foundation for a follow-up job that will automate cutting and publishing releases. Change-Id: I34a36ef8c33599cbf70d797468d65eb43a1af957
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/