| commit | 4041dd87c76f3af7827b14e13377ea647d07d93e | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Thu Dec 10 15:13:32 2020 +0000 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu Dec 10 15:13:32 2020 +0000 |
| tree | 49adde10b9e6e0f730b6fc4baada71ade24359dc | |
| parent | 847cf76f7f27acfb79c9279e91f18b585c199ddf [diff] |
Remove obsolete Bazel spawn strategies After the latest Bazel upgrade, the --spawn_strategy=standalone doesn't show the output of the subprocess created, making the troubleshoot of the failures impossible. The sandboxing was introduced many years ago with Change-Id: I15bc00861 because of the initial limitations of sandboxing with Docker. With the recent versions of Bazel this legacy flags shouldn't be needed anymore. Change-Id: I0a68895b57d3d6f066de3ac9420a00f2e02a09c8
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/