-
Notifications
You must be signed in to change notification settings - Fork 1.9k
STOR-2413: Periodics tests in Sippy #66610
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
base: master
Are you sure you want to change the base?
Conversation
@dfajmon: This pull request references STOR-2413 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 openshift-eng/jira-lifecycle-plugin repository. |
Update periodic tests to their respective files. Enable tests to be visible in Sippy.
Update periodic tests to their respective files. Enable tests to be visible in Sippy.
Update periodic tests to their respective files. Enable tests to be visible in Sippy.
Update periodic tests to their respective files. Enables tests to be visible in Sippy.
[REHEARSALNOTIFIER]
A total of 38 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
@dfajmon: 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. |
ci-operator.openshift.io/variant: periodics | ||
ci.openshift.io/generator: prowgen | ||
pj-rehearse.openshift.io/can-be-rehearsed: "true" | ||
name: pull-ci-openshift-gcp-filestore-csi-driver-operator-release-4.19-periodics-ci-index-gcp-filestore-csi-driver-operator-bundle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does a periodic job have pull-
prefix + is in presubmits.yaml
? There are many such jobs now, probably related to OLM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is related to all periodic jobs containing bundles. I will have to look more in-depth as to why it generates it that way.
This PR addresses STOR-2413 by making Storage periodic tests visible in Sippy and cleaning up unused periodics to improve resource utilization and test visibility.
I have added Slack reporter config to our components for future proofing, so we can add periodic test reporters more easily.
Removed old running jobs that are no longer necessary.