| commit | aecb2d2ab1a5132d6375f0c8e6922958911d1021 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Tue Apr 19 10:22:31 2022 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue Apr 19 10:22:31 2022 +0100 |
| tree | 929ff2f665f1c26b16359c5efc99c5e47c0bec7c | |
| parent | 6c924b47c0347e304bdf4ba9deae475a92a4a9cd [diff] |
Execute plugins on Bazel-capable agents by default Some of the plugins' builds are derived directly from the top-level default template which did not contain a node label, causing it to run on the Jenkins coordinator. Use a default agent label that would always direct the execution to a Bazel agent. Change-Id: I66cc4271b4332fdf38dcb7765c03619e44695445
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/