adding updates for prow in 5.1 - #83187
Conversation
Signed-off-by: kurwang <kurwang@redhat.com>
|
/hold wait until branch day |
openshift-ci
Bot
added
the
do-not-merge/hold
Remove disabled: true from release-5.0 promotion so the release branch actively produces its own 5.0 images, aligning with mtv-integrations and other components that have already enabled it. Co-authored-by: Cursor <cursoragent@cursor.com>
|
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: Pro Plus Run ID: ⛔ Files ignored due to path filters (5)
📒 Files selected for processing (6)
💤 Files with no reviewable changes (1)
WalkthroughThe PR adds release 5.1 CI configurations and protected-branch checks for ChangesRelease CI configuration
Estimated code review effort: 3 (Moderate) | ~20 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kurwang 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 |
|
@kurwang: |
|
[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: |
|
@kurwang: 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. |
1 participant
Summary
multicluster-role-assignment
1. New CI operator config for release-5.1
stolostron-multicluster-role-assignment-release-5.1.yaml— exact copy of the 5.0 config withpromotion.namechanged to"5.1"anddisabled: trueset (bootstrap posture until main is retargeted to a future release)2. Updated prowconfig branch protection
mainbranch: Konflux checks updated fromacm-50→acm-51(since main now targets the 5.1 development cycle)release-5.1branch protection requiringacm-51Konflux checks (enterprise-contractandon-pull-request)3. Generated Prow jobs
release-5.1-presubmits.yamlandrelease-5.1-postsubmits.yamlauto-generated bymake updatemtv-integrations
1. New CI operator config for release-5.1
stolostron-mtv-integrations-release-5.1.yaml— copy of the 5.0 config withpromotion.namechanged to"5.1"anddisabled: trueadded2. Removed fast-forward from main
fast-forwardpostsubmit job frommain.yamlthat was forwardingmain→release-5.0(per the Jira ticket warning: "If fast-forwarding is configured in 5.0, this needs to be disabled")3. Updated prowconfig branch protection
mainbranch: Addedacm-51Konflux checks (previously had none, onlyprotect: true)release-5.1branch protection requiringacm-51Konflux checks4. Generated Prow jobs
release-5.1-presubmits.yamlandrelease-5.1-postsubmits.yamlauto-generatedmain-postsubmits.yamlregenerated (fast-forward job removed)Summary by CodeRabbit
mtv-integrationsandmulticluster-role-assignment.multicluster-role-assignmentrelease-5.0 promotion.mtv-integrationsmainfast-forward postsubmit torelease-5.0.