Export logs to S3 when running gatling-gerrit-test

When running gatling tests against gerrit it is useful to make the logs
of the execution available to Jenkins so that further investigations and
analysis can be performed in case of regressions or failures.

Add an additional stage in which logs are exported from CloudWatch to S3
by running the aws-gerrit command `export-logs`.

The output of the publicly available logs will be outputted in the
console so that it can be retrieved if needed.

Bug: Issue 14450
Change-Id: Iae0d8035d8fcc2845a75a0fd7c524d04ec2a9d01
2 files changed
tree: a78962ec416f7e7b3eb8dfe845aa0acc70780d97
  1. .gitignore
  2. Jenkinsfile
  3. README.md
  4. jenkins-docker/
  5. jenkins/
  6. vars/
  7. worker/
  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/