Separate Jenkins config.xml for internal and external setup

Ensure that Jenkins external/internal configurations contain only the
settings necessary for hosting jobs. This separation helps to minimize
potential security risks.

Bug: Issue 16988
Change-Id: Idde756ad53311936ca514495e10625ba631a9f88
3 files changed
tree: 6cd4532da8edb56f78ca881a88e93347bcc52275
  1. jenkins/
  2. jenkins-docker/
  3. jenkins-internal/
  4. vars/
  5. .gitignore
  6. Jenkinsfile
  8. yamllint-config.yaml

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] [2]