| commit | 8c1636d037bd1870904e2a72fa5954d8d7138028 | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Tue Sep 30 11:44:44 2025 +0200 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu Oct 02 04:57:49 2025 -0700 |
| tree | 1661cf54420925164160e6a77dd8eed4d598c29c | |
| parent | b3a58cde2da87c02b7a2b42f87d4a90a031e2d0e [diff] |
release: consume .gitconfig.template from secret file Update `gerrit-release.sh` to consume `.gitconfig` from the location specified by `$GITCONFIG_TMPL` instead of assuming it is mounted at `$HOME/.gitconfig.template`. Previously, the file had to be manually mounted as a Docker volume, which does not align with the goal of a fully automated release pipeline. With this change, `.gitconfig` can be provided securely through Jenkins vault as a secret file, enabling non-interactive and automation-friendly release workflows. Change-Id: Ie7c30ccec5ca24dab73d01a2691d0c88b93dc424
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/