WINC-1869: replace WS2019 for WS2025 in azure-e2e job#77975
WINC-1869: replace WS2019 for WS2025 in azure-e2e job#77975openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Conversation
this commit removes Windows Server 2019 job references and update to Windows Server 2025 from periodic to presubmit in configuration files
|
@jrvaldes: This pull request references WINC-1869 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 "5.0." or "openshift-5.0.", but it targets "WMCO 10.22.0" instead. 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
💤 Files with no reviewable changes (4)
WalkthroughUpdates Windows Machine Config Operator CI pipeline configurations to deprecate Windows Server 2019 testing and standardize on Windows Server 2025. Changes include removing legacy 2019-based job definitions, deleting associated periodic cron jobs, and updating remaining test configurations to target the newer Windows Server version. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 10✅ Passed checks (10 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@jrvaldes: This pull request references WINC-1869 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 "5.0." or "openshift-5.0.", but it targets "WMCO 10.22.0" instead. 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. |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-azure-e2e-operator |
|
@jrvaldes: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-azure-e2e-operator |
|
@jrvaldes: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@jrvaldes: job(s): either don't exist or were not found to be affected, and cannot be rehearsed |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jrvaldes, mansikulkarni96 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/pj-rehearse ack |
|
@jrvaldes: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@jrvaldes: 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 pull request updates the CI configuration for the Windows Machine Config Operator by removing all references to Windows Server 2019 end-to-end (e2e) Azure tests and associated periodic jobs, and migrating the remaining e2e tests to use Windows Server 2025. These changes ensure that only Windows Server 2025 is tested in the relevant release branches and that obsolete jobs are cleaned up.
Summary by CodeRabbit
Tests
Chores