Adopt modern Jenkins terminology for build agents

The Jenkins terminology has been updated over a year
ago (see [1]) and it is time to align all our images
and builds to the new and more respectful term of agent
to refer to build workers.

[1] https://www.jenkins.io/blog/2020/06/18/terminology-update/

Change-Id: I8e9246f6d06d2a93d5ab612843fc41b41e47ccf3
35 files changed
tree: 37ea07edab30437dab35f5a13d8439f8250a377a
  1. .gitignore
  2. Jenkinsfile
  3. README.md
  4. jenkins-docker/
  5. jenkins/
  6. vars/
  7. worker/
  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/