Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated readme with details about the upgrade tests #1301

Merged
merged 1 commit into from
Jul 2, 2024
Merged

Updated readme with details about the upgrade tests #1301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -429,9 +429,11 @@ To trigger the E2E test for each new Release added in a PR add a comment with th

`/run releases-test-suites`

This will automatically trigger tests for all new releases detected in the PR and will run them against the appropriate `standard` test suite for the provider.
This will automatically trigger tests for all new releases detected in the PR and will run them against the appropriate `standard` and `upgrade` test suites for the provider.

If you need to run tests for a specific Release (from the PR) or a different test suite you can do so with the two following, optional parameters:

* `TARGET_SUITES` - a comma separated list of test suites to trigger (e.g. `./providers/capa/standard`)
* `TARGET_RELEASES` - a comma separates list of Releases to trigger from the PR (e.g. `aws-25.0.0-example.1`)

The `upgrade` tests will first install a cluster using the latest previously published release and then upgrade to using the release found in the PR. If you need to override the starting Release version (to test upgrading from an earlier release) you can do so by setting the `PREVIOUS_RELEASE` parameter on the trigger comment (e.g. `/run releases-test-suites PREVIOUS_RELEASE=aws-v25.0.0`)
Loading