Gatling Gerrit: Generate unique target URL

When deploying gerrit in AWS, a new DNS 'A' entry is created with a
domain name such as "jenkins-master-demo.gerrit-demo.gerritforgeaws.com"

During subsequent runs of the gerrit-gatling job however, this DNS cache
resolution might still be cached, effectively preventing jenkins to
resolve the new URL.

Create unique target URLs, such as
"jenkins-<timestamp>.gerrit-demo.gerritforgeaws.com" so that each run is
independent from any previous execution.

Bug: Issue 14192
Change-Id: I464e2e17b4239c2066f25fb3e6566c458d9cba56
1 file changed
tree: 5fb1ffe88157a988e2e3bd9673f1d8c89549cd6b
  1. jenkins-docker/
  2. jenkins/
  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/