Introduce gerritJGitServlet4Pipeline library

The Bazel-based build of JGit has historically been unmonitored, leading
to unnoticed breakages due to lack of CI validation. Currently, the
Eclipse CI pipeline only verifies Maven builds, which does not cover all
scenarios.

Introduce a new `gerritJGitServlet4Pipeline` and a job to leverage it
ensure that JGit servlet-4 branch builds with Gerrit so that we can spot
JGit servlet-4 changes that are incompatible with Gerrit before they get
merged.

Change-Id: I5f508fc2e15ab98c7cadd5e88fee14d459d90c42
1 file changed
tree: cc828346db48fb380153caff548744e866034a17
  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/