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
OCPCLOUD-2121: Add openshift/e2e-tests for CAPI E2E testing #465
OCPCLOUD-2121: Add openshift/e2e-tests for CAPI E2E testing #465
Conversation
@damdo: This pull request references OCPCLOUD-2121 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @JoelSpeed |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This change only introduces a script which doesn't affect the payload. |
@damdo: Overrode contexts on behalf of damdo: ci/prow/e2e-aws-serial, ci/prow/e2e-hypershift In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@damdo: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
This PR adds a script under
openshift/e2e-tests.sh
which can be invoked manually or through the OpenShift CI steps (as we already do for unit tests) to launch CAPI E2E tests from within the provider repo.This mimics the approach in the MAPI providers where we clone the repo where the e2e tests reside and launch those from within the provider repo PRs.