Update plugin pipeline google-java-format defaults

Gerrit core uses different default google-java-format versions depending
on the target branch. Keep the plugin pipeline aligned with those
defaults by using 1.24.0 for stable-3.11 through stable-3.14 and 1.35.0
for master and future stable branches.

The formatter binaries are now preinstalled in the Bazel agent image.
Remove the temporary gerrit-tools clone and per-build formatter setup
from the formatting stage. This avoids an extra clone from googlesource
on every plugin formatting check and relies on the image-provided tools
instead.

The gjfVersion parameter is still honored, so callers can override the
branch-based default when needed.

Change-Id: I2273e6eb7f3890242cccdb5a94b7ac6582fcb35f
1 file changed
tree: 25b7012b331f3a04be5272653c84e4d33319e4c0
  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/