commit | 5bbb962d2b8498d576c59af33693eba774bbaa90 | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Tue Oct 06 16:07:10 2020 +0100 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue Oct 06 15:09:45 2020 +0000 |
tree | c155d7fab6d5deefb2067a02b693cb81578a2726 | |
parent | ca25e4e906a9879d3c31fca5071c61f445a1ede4 [diff] |
Use remote Bazel Java11 JDK on Gerrit-CI for master Gerrit-CI build agents do not have yet a local Java 11 setup and therefore would still need to use a remote JDK provided dynamically by Bazel. Without the remote JDK, the acceptance tests would fail because of class version incompatibility. Change-Id: Ibe2f0a4b034354f42578a225e15689e1aed0969c
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/