| commit | ee5bfe78080757fb874e3bb1dc3c4899ee47e9ae | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Wed Oct 08 21:11:37 2025 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu Oct 09 12:15:36 2025 -0700 |
| tree | 31debf012db7dff01b16d044f9c503a36e0e5aaf | |
| parent | 0358c8747207457cd8855d0113adbda714e7e7b6 [diff] |
gerrit-release: consume GPG_KEY as a string credential The configuration of string credentials is already implemented in the Jenkins secrets loading mechanism, therefore, it is easier to store directly the full content of the GPG key in the secrets rather than relying on the file credentials. Also, use envsubst for storing the variable into a file and avoid the accidental display of the private key on the script output. Change-Id: If800219a340a98f893e61a374d683787e649de64
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/