OCPQUAL-34: Disable EOL openshift-tests-private upgrade jobs - #83628
Open
jogeo wants to merge 1 commit into
Open
OCPQUAL-34: Disable EOL openshift-tests-private upgrade jobs#83628jogeo wants to merge 1 commit into
jogeo wants to merge 1 commit into
Conversation
…ng cron to Feb 30. The 4.13/4.15/4.17 upgrade jobs test versions that have reached end of life. Disable them by setting each cron entry to February 30th, preserving the configuration but never running the job. Applies to openshift-tests-private configs matching "4.1[357]-upgrade" or "upgrade-from-stable-4.1[357]". 885 periodic jobs across 58 config files disabled. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
openshift-ci-robot
added
the
jira/valid-reference
Contributor
|
@jogeo: This pull request references OCPQUAL-34 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 the "5.1.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
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 (8)
📒 Files selected for processing (58)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe pull request updates cron expressions for OpenShift upgrade test jobs in releases 4.13–4.22. Most schedules move to February 30 while preserving execution times and job configuration. Some 4.21 jobs move to March 30 or June 30. ChangesUpgrade test cron schedules
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: 🔵 Low · up to The change parks 885 end-of-life upgrade jobs by assigning impossible cron dates. It is mergeable with owner awareness that the affected configurations still require repository generation and validation so deployed job definitions and metadata use the disabled schedules. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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
|
[REHEARSALNOTIFIER]
A total of 885 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. |
Open
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
2 participants
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.
The 4.13/4.15/4.17 upgrade jobs test versions that have reached end
of life. Disable them by setting each cron entry to February 30th,
preserving the configuration but never running the job.
Applies to openshift-tests-private configs matching "4.1[357]-upgrade"
or "upgrade-from-stable-4.1[357]".
885 periodic jobs across 58 config files disabled.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
Summary by CodeRabbit