Allow passing extra Bazel options to plugin builds

Add support for passing additional Bazel options from plugin build jobs
to the build scripts and pipeline helpers.

In some cases a plugin may need to pass additional Bazel configuration
options during the plugin build.

A typical use case is to enforce building with an older Java version
after the master branch has switched to a newer one.

Change-Id: I1b6b7a9f450fd91568fb7a42772d404d8046edd8
3 files changed
tree: 5339a10d79fdcfca5ecac5483f04a49e58b8b058
  1. jenkins/
  2. jenkins-docker/
  3. jenkins-internal/
  4. vars/
  5. .gitignore
  6. Jenkinsfile
  7. README.md
  8. yamllint-config.yaml
README.md

Gerrit CI scripts

Providing jobs

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/