Fix JJB expansion of shell parameter syntax
Jenkins Job Builder treats {} as template expansion markers. In the
Bazel major-version check, this interferes with the shell parameter
expansion ${BAZEL_MAJOR:-0} used to provide a default value.
Escape the expression by doubling the braces so JJB preserves it
verbatim in the generated job scripts.
This keeps the Bazel >= 9 conditional working as intended in both
Jenkins shell wrappers.
Change-Id: I310b726c580c1658f585ddc25772d39207d3bc13
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/