| commit | e0c046cc6adb95960c2531cebe7d1ce188b7f6cb | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Thu Oct 13 21:23:40 2022 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Mon Oct 17 08:53:12 2022 +0000 |
| tree | 91d9ec35923a8a5c5758ce180c37ef0530130ca7 | |
| parent | 44bc53cff4daf13f7d0c0b8cbf00b035aa9a1fb0 [diff] |
Prevent random Java 11 crashes during Bazel executions Bazel and Java 11 can crash randomly due to the overload of files generated in the in-memory temporary directory. Use the well-known workaround documented at [1] by using a filesystem-based temporary directory for Bazel executions. The problem appears on Java 11 only, therefore the Java 8 Bazel options are left as-is. [1] https://github.com/bazelbuild/bazel/issues/3236 Change-Id: I9308d710ea96e750439ce5fd37e97c67d8dbcbc8
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/