| commit | aca0c2c15467a8af89f862a1da72f7b0f9664faa | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Wed Mar 03 17:43:33 2021 +0100 |
| committer | Antonio Barone <syntonyze@gmail.com> | Thu Mar 04 17:17:57 2021 +0000 |
| tree | d7b05d1b71d7226e42431c130d36f28d51ce8225 | |
| parent | 79193b6b9460cba593aeba429f24b5754a735a0c [diff] |
Quote and qualify parameters explicitly The gatling test job worked correctly when explicitly built with parameters via the Jenkins UI, however when triggered by Jenkins itself, it was failing due to "MissingPropertyException: No such property". Always quoting and fully qualify parameters explicitly as documented by the `parameters` documentation[1] resolves the issue and allows the job to trigger without human intervention. [1]https://www.jenkins.io/doc/book/pipeline/syntax/#parameters Bug: Issue 14181 Change-Id: Ifa458f31faecc07c314173bcce941d4a89d55699
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 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/