Optimize pipelines performance cron schedule with variant-based grouping - #81738
Conversation
|
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 (2)
📒 Files selected for processing (1)
WalkthroughOpenShift Pipelines performance cron schedules were updated across nightly, pipeline-version, signing, and resource-pruning jobs. Several 1.19 max-concurrency job definitions were removed while corresponding 1.20 definitions and deployment version values were retained or updated. ChangesOpenShift Pipelines performance configuration
Estimated code review effort: 3 (Moderate) | ~25 minutes Suggested labels: Suggested reviewers: 🚥 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 |
|
[REHEARSALNOTIFIER]
A total of 40 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: |
|
/pj-rehearse ack |
|
@deekshith-24: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-merge-bot
Bot
added
the
rehearsals-ack
|
/approve |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deekshith-24, siddardh-ra 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 |
openshift-ci
Bot
added
the
approved
|
@deekshith-24: 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. |
![openshift-prow[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
2 participants
Summary
Optimizes the OpenShift Pipelines performance cron schedule to reduce CI infrastructure saturation on
aws-pipelines-performanceBoskos pool.Changes
Schedule Architecture
Concurrency Impact
Why variant-based grouping?
When filtering Grafana by
deploy_config = Standard, all version data points (nightly, 1.20, 1.21, 1.22) land on the exact same dates -- perfect alignment for side-by-side version comparison in KB articles and performance docs.Summary by CodeRabbit
Reorganized OpenShift Pipelines performance CI schedules to reduce saturation in the
aws-pipelines-performanceBoskos pool. Jobs are grouped by deployment variant and distributed across dedicated day-of-month and two-hour time slots, while selected days retain full nightly regression coverage.Removed periodic and optional Pipelines 1.19 jobs, updated coverage for Pipelines 1.20 variants, and scheduled Tkn-res jobs daily in a dedicated block. This lowers peak concurrency and aligns deployment-variant data points for comparison.