Disable infrequent openshift-tests-private jobs#80876
Open
jogeo wants to merge 1 commit into
Open
Conversation
…t they can not be monitored from Sippy Component Readiness.
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jogeo The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (12)
📒 Files selected for processing (235)
WalkthroughAcross CI configuration files for OpenShift releases 4.12 through 4.16, all per-job ChangesCron normalization across releases 4.12–4.16
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
|
Contributor
|
[REHEARSALNOTIFIER]
A total of 8088 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: |
Contributor
|
@jogeo: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are many QE jobs configured to run cases from openshift-tests-private. Anything that runs with a frequency greater than weekly, falls outside the window monitored by component readiness. This is a huge commit that disables all these jobs. This is a big step toward the desire to consolidate all test monitoring into a single instance of Sippy and the direction that has been proposed by the Next Generation Quality Working Group.
Summary by CodeRabbit
This PR disables a large set of OpenShift quality assurance (QE) test jobs by standardizing their cron schedules to an impossible date (
0 0 31 2 *— February 31st), effectively preventing them from running. The changes affect theopenshift-tests-privaterepository's CI configuration across all currently supported release branches (4.12 through 4.16).Scope of Changes:
ci-operator/config/openshift/openshift-tests-private/Target Jobs:
The PR targets QE jobs that previously ran at infrequent intervals (frequencies greater than weekly) — such as jobs scheduled for every 2-3 months or with irregular patterns. These jobs fell outside the monitoring window of Sippy, OpenShift's quality metrics tracking system.
Purpose:
This consolidates test monitoring into a single Sippy instance, aligning with the Next Generation Quality Working Group's direction for centralized quality assurance infrastructure. By disabling these infrequently-running jobs, the PR removes noise from the monitoring system and focuses resources on tests that run within Sippy's monitoring window.
Additional Details:
In a few configuration files (notably around IBM Cloud and vSphere job blocks), the changes include minor structural adjustments to clean up duplicated or misaligned job definitions alongside the cron schedule updates, ensuring consistent YAML structure across the affected configurations.