Gatling tests use LDAP authentication

Testing gerrit with DEVELOPMENT_BECOME_ANY_ACCOUNT does not represent a
very realistic use-case, since such authentication type is not used in a
real production deployment.

Setup instead a Gerrit instance configured to talk to a real LDAP
server.

LDAP parameters can be configured. By default point to a GerritForge
deployment.

Bug: Issue 15308
Change-Id: I4c95edad9b2eaf0e965fd9f42d973edf61147bfd
1 file changed
tree: bc674a43d39bfe1ba4710d53758a11ffd1a6ade0
  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/