ci-operator/step-registry/ipi/ipi-workflow: Drop install-only workflow #7299
Conversation
Job authors who need their own end-to-end test logic will need to define their own workflow, like a2fd8c3 (step-registry: add Origin E2E test step, 2020-01-31, openshift#6965) did for origin-e2e. There's no way to piggy-back on a generic workflow to inject a custom test; but you can lean on existing pre and post chains.
openshift-ci-robot
added
the
size/S
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
@AlexNPavel pointed out that you can use the - as: org-repo-e2e
steps:
cluster_profile: aws
workflow: ipi
test:
- ref: org-repo-e2e/close |
|
@wking: Closed this PR. DetailsIn 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. |
2 participants
Job authors who need their own end-to-end test logic will need to define their own workflow, like a2fd8c3 (#6965) did for origin-e2e. There's no way to piggy-back on a generic workflow to inject a custom test; but you can lean on existing pre and post chains.