d40f5d3089
This adds upgrade testing from our current Gerrit version (3.5) to the likely future version of our next upgrade (3.6). To do so we have to refactor the gerrit testing becase the 3.5 to 3.6 upgrade requires we run a command against 3.5. The previous upgrade system assumed the old version could be left alone and jumped straight into the upgrade finally testing the end state. Now we have split up the gerrit bootstrapping and gerrit testing so that normal gerrit testing and upgrade testing can run these different tasks at different points in the gerrit deployment process. Now the upgrade tests use the bootstrapping playbook to create users, projects, and changes on the old version of gerrit before running the copy-approvals command. Then after the upgrade we run the test assertion portion of the job. Change-Id: Id58b27e6f717f794a8ef7a048eec7fbb3bc52af6 |
||
|---|---|---|
| .. | ||
| gerrit | ||
| infra-puppet-apply | ||
| infra-puppet-beaker-rspec | ||
| roles/encrypt-logs | ||
| templates | ||
| bootstrap-and-test-review.yaml | ||
| bootstrap-test-review.yaml | ||
| run-base-post.yaml | ||
| run-base-pre.yaml | ||
| run-base.yaml | ||
| run-lists-post.yaml | ||
| run-production-playbook.yaml | ||
| test_gerrit_renames.yaml | ||
| test_gitea_renames.yaml | ||
| test-review.yaml | ||
| upgrade-review.yaml | ||