Do not use GitHub as SCM source but rely on GerritHub.io URL

Use GerritHub.io URL and associated credentials for fetching projects
that are hosted on GerritHub, without having to rely on GitHub URLs.

Use GH_* credentials for GerritHub and keep GS_* credentials
for Gerrit-Review, storing them onto the $HOME/.netrc during
the build.

Change-Id: I9415f771e6f7976e1dc5a324e966bf11f115bddb
10 files changed
tree: 38783d14ff593ae5ff780fb26d523e89c905dd12
  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/