| commit | 23744347f246c66a8cf95f47bbd04f142703b236 | [log] [tgz] |
|---|---|---|
| author | Jacek Centkowski <geminica.programs@gmail.com> | Fri Apr 19 06:56:55 2024 +0200 |
| committer | Jacek Centkowski <geminica.programs@gmail.com> | Mon Apr 22 06:08:11 2024 +0000 |
| tree | 86fae2b0aabc29c13ad0f9d990dc92cdad691a46 | |
| parent | 369a70f74637f0b6858cfaaff94b04e546910454 [diff] |
Fix gh-get-plugin-info action to use repo instead of name For GitHub related steps we have both `repo` and `name` defined for the cases when they are different. Ensure that `gh-get-plugin-info` step uses `repo` in curl's http address to get details. The step is also used in `gerrit-eca-plugin` and `redirect-change-number` plugins and in these cases `repo == name` hance it doesn't affect the build. Change-Id: Ifc3aa9c4d15b7b14c6b057e403c6a7ebf776b250
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/