Default params for gatling against single-master gerrit

Add missing default parameters to allow testing a single Gerrit instance
in AWS with Gatling.

The deployment uses a 'jenkins' user in the GerritForge AWS account,
which has the relevant permissions to create and destroy the stack.

Gatling HTTP username and password are retrieved from the vault.

Bug: Issue 13829
Change-Id: I443a82aab2175ff157e2e7f59ca02184dbfd2417
1 file changed
tree: eb58b609a1954c227ebe7926402519847f0bfd9d
  1. jenkins/
  2. jenkins-docker/
  3. vars/
  4. worker/
  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 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]