-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OPRUN-3878: release-4.18: Add periodics for openshift-operator-framework-olm-release #64511
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
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: camilamacedo86 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@camilamacedo86: This pull request references Jira Issue OCPBUGS-55696, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
8d81520
to
def9abe
Compare
@camilamacedo86: This pull request references OPRUN-3878 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 bug to target the "4.20.0" version, but no target version was set. 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. |
/jira refresh |
@camilamacedo86: This pull request references OPRUN-3878 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 bug to target the "4.20.0" version, but no target version was set. 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. |
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
@camilamacedo86: 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. |
Compared to the
Why? |
Hi @tmshort We are doing the same thing that was done for 4.17. We have introduced changes regarding the monorepo initiative. So, I suggest that we add the periodic for 4.18 as it is for 4.17, and then, if we need to add any other tests for 4.18 that do not exist for 4.17, we can go in a follow-up. WDYT? |
Is this even the right location? Shouldn't these be in operator-framework-operator-controller if we're looking for default catalog test support? |
Close that was a mistake |
No description provided.