Workaround for allowing BuildBuddy fetch of the Docker build image After the upgrade of the on-prem BuildBuddy runner to enterprise-v2.312.0, the fetch of the container specified in Gerrit's tools/remote/BUILD under the platform's exec_properties container-image. See the official BuildBuddy documentation on how to use credentials for fetching Docker images from GCR at [1]. [1] https://www.buildbuddy.io/docs/rbe-platforms/ Change-Id: I75db4ca8526cdcb6a85b8aacb9e350705a3ab9f4
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/