-
Notifications
You must be signed in to change notification settings - Fork 1.9k
CM-424: [o/cert-manager-operator] moved e2e test cases for TechPreview features #60386
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
CM-424: [o/cert-manager-operator] moved e2e test cases for TechPreview features #60386
Conversation
@swghosh: This pull request references CM-424 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.19." or "openshift-4.19.", but it targets "cert-manager-1.15" instead. 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 openshift-eng/jira-lifecycle-plugin repository. |
Skipping CI for Draft Pull Request. |
9d16b8b
to
b13c5b6
Compare
/retest |
Issues in openshift/release go stale after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
b13c5b6
to
27e87c0
Compare
/cc @bharath-b-rh |
/lgtm |
@swghosh: This pull request references CM-424 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.19." or "openshift-4.19.", but it targets "cert-manager-1.15" instead. 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 openshift-eng/jira-lifecycle-plugin repository. |
27e87c0
to
9fb832b
Compare
also, cc: @PillaiManish |
@bharath-b-rh not sure what's causing the ordered prow config issue, I have re-run Meanwhile, |
@swghosh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
d88a182
to
e7ff3e2
Compare
…tures Signed-off-by: Swarup Ghosh <[email protected]>
e7ff3e2
to
4a460c5
Compare
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse |
@swghosh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse ack |
@swghosh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bharath-b-rh, swghosh 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 |
@swghosh: 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-sigs/prow repository. I understand the commands that are listed here. |
Adds an optional e2e test job for o/cert-manager-operator,
test cases are filtered by the Ginkgo
TechPreview
label filter.With this change the tech-preview e2e(s) will only be triggered when certain files which affect the TP features are changed.