-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
CAPA: Release v27.4.0. #1519
CAPA: Release v27.4.0. #1519
Conversation
/run releases-test-suites PREVIOUS_RELEASE=27.3.0 |
releases-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a Alternatively, or in addition to, you can also specify |
/run releases-test-suites PREVIOUS_RELEASE=27.3.0 |
releases-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a Alternatively, or in addition to, you can also specify |
/run releases-test-suites PREVIOUS_RELEASE=27.3.0 |
releases-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a Alternatively, or in addition to, you can also specify |
I'm skipping CI as I had to rebase this branch on top of master and don't want to run tests again just for this. |
Checklist
Triggering E2E tests
To trigger the E2E test for each new Release added in this PR, add a comment with the following:
/run releases-test-suites
If you want to trigger conformance tests, you can do so by adding a comment similar to the following:
/run conformance-tests PROVIDER=capa RELEASE_VERSION=29.1.0
For more details see the README.md.