Pipeline: use basic authentication when talking to Gerrit

The credential id used in the Jenkins pipeline is propagated
downstream to the pipeline script: reuse the same credentials
for any subsequent interaction with Gerrit via REST-API for
retrieving further change details.

Change-Id: Ia999297b4ece802a089971c3c9880c9d35bb8ec6
1 file changed
tree: c98ba5d4751218cb66ba1e917f641103dbdccb5c
  1. jenkins/
  2. jenkins-docker/
  3. vars/
  4. worker/
  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 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/