Skip to content

MULTIARCH-6023: Update CI schedule: run 5.0 builds on weekdays and 4.23 builds every Saturday - #83054

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
raja-0940:main
Aug 10, 2026
Merged

MULTIARCH-6023: Update CI schedule: run 5.0 builds on weekdays and 4.23 builds every Saturday#83054
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
raja-0940:main

Conversation

@raja-0940

@raja-0940 raja-0940 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

This PR resolves the scheduling conflicts between the 4.23 and 5.0.0 CI nightly builds

Before this change:

  • Both builds were scheduled to run on odd numbered days, resulting in a schedule conflict.

After this change:

  • 4.23.0 nightly builds will run on odd- numbered days.
  • 5.0.0 nightly builds will run on even-numbered days.

Summary by CodeRabbit

  • Updated the OpenShift PowerVS OVN multi-architecture nightly job schedules.
  • The 5.0.0 build now runs at 06:00 UTC on weekdays.
  • The 4.23.0 build now runs at 06:00 UTC every Saturday.
  • These schedules prevent conflicts between the 5.0.0 and 4.23.0 builds.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

The PowerVS OVN multi-architecture test job schedules changed for the 4.23 and 5.0 nightly configurations.

Changes

PowerVS OVN schedule updates

Layer / File(s) Summary
Update the nightly cron schedules
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23.yaml, ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
The 4.23 job now runs Saturdays at 06:00 UTC. The 5.0 job now runs Monday through Friday at 06:00 UTC.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: deepsm007, chidanandbh

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The patch changes only cron fields in three YAML files; added-line searches found no Ginkgo title calls or dynamic test-title expressions.
Test Structure And Quality ✅ Passed The PR changes only YAML cron schedules and generated periodic job data; no Ginkgo test code or It blocks are present, so this check is not applicable.
Microshift Test Compatibility ✅ Passed The commit changes only three YAML CI schedule files; it adds no Go files or Ginkgo test declarations, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR changes only three CI YAML schedule entries; no Ginkgo test declarations or test-like files were added or modified, so SNO compatibility review is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The patch changes only CI cron expressions in three ci-operator YAML files; it adds no deployment manifests, operator code, controllers, or topology-sensitive workload constraints.
Ote Binary Stdout Contract ✅ Passed The PR changes only YAML cron schedules in two configs and the generated periodics file; no OTE binary or process-level stdout code is added or modified.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The commit changes only cron schedules in two configuration files and one generated periodics file; it adds no Ginkgo tests or networking/external-connectivity code.
No-Weak-Crypto ✅ Passed The PR changes only cron schedules in three YAML files; no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret comparisons were added.
Container-Privileges ✅ Passed The PR changes only cron schedules in two ci-operator configs and one generated periodics file; no privileged, host namespace, SYS_ADMIN, root, or allowPrivilegeEscalation settings were added.
No-Sensitive-Data-In-Logs ✅ Passed The complete patch changes only cron expressions in two configs and one generated periodics file; it adds no logging statements or sensitive values.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the CI schedule changes for 5.0 and 4.23 builds.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from chidanandbh and deepsm007 August 6, 2026 15:49

@prb112 prb112 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/cc @prb112
missing one additional file change

There is a main prow config in the folder that needs updating.

@openshift-ci
openshift-ci Bot requested a review from prb112 August 6, 2026 16:36
@prb112

prb112 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

/retitle MULTIARCH-6023: Update CI schedule: run 5.0.0 nightly builds on even days

@openshift-ci openshift-ci Bot changed the title Update CI schedule: run 5.0.0 nightly builds on even days MULTIARCH-6023: Update CI schedule: run 5.0.0 nightly builds on even days Aug 6, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 6, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

@raja-0940: This pull request references MULTIARCH-6023 which is a valid jira issue.

Details

In response to this:

This PR resolves the scheduling conflicts between the 4.23 and 5.0.0 CI nightly builds

Before this change:

  • Both builds were scheduled to run on odd numbered days, resulting in a schedule conflict.

After this change:

  • 4.23.0 nightly builds will run on odd- numbered days.
  • 5.0.0 nightly builds will run on even-numbered days.

Summary by CodeRabbit

  • Updated the OpenShift PowerVS OVN multi-architecture nightly job schedule.
  • The 5.0.0 build now runs on even-numbered days from 2 through 30.
  • This separates the 5.0.0 schedule from the 4.23.0 builds, which run on odd-numbered days.

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.

@prb112

prb112 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

See https://github.com/openshift/release/pull/76255/changes

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@prb112 prb112 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it'll work. 4.23 is the problem - let's schedule this for Saturdays, and run 5.0 M through F.

…Saturday

Signed-off-by: Rajakumar Battula <rbattula@redhat.com>
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@raja-0940: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-powervs-ovn-multi-p-px N/A periodic Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-e2e-powervs-ovn-multi-p-px N/A periodic Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@raja-0940: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-e2e-powervs-ovn-multi-p-px N/A periodic Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-powervs-ovn-multi-p-px N/A periodic Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

1 similar comment
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@raja-0940: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-e2e-powervs-ovn-multi-p-px N/A periodic Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-powervs-ovn-multi-p-px N/A periodic Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@raja-0940

raja-0940 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/retitle MULTIARCH-6023: Update CI schedule: run 5.0 builds on weekdays and 4.23 builds every Saturday

@openshift-ci openshift-ci Bot changed the title MULTIARCH-6023: Update CI schedule: run 5.0.0 nightly builds on even days [MULTIARCH-6023](https://redhat.atlassian.net/browse/MULTIARCH-6023): Update CI schedule: run 5.0 builds on weekdays and 4.23 builds every Saturday Aug 10, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@raja-0940: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

This PR resolves the scheduling conflicts between the 4.23 and 5.0.0 CI nightly builds

Before this change:

  • Both builds were scheduled to run on odd numbered days, resulting in a schedule conflict.

After this change:

  • 4.23.0 nightly builds will run on odd- numbered days.
  • 5.0.0 nightly builds will run on even-numbered days.

Summary by CodeRabbit

  • Updated the OpenShift PowerVS OVN multi-architecture nightly job schedules.
  • The 5.0.0 build now runs at 06:00 UTC on weekdays.
  • The 4.23.0 build now runs at 06:00 UTC every Saturday.
  • These schedules prevent conflicts between the 5.0.0 and 4.23.0 builds.

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.

@raja-0940

raja-0940 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/retitle MULTIARCH-6023: Update CI schedule: run 5.0 builds on weekdays and 4.23 builds every Saturday

@prb112

prb112 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

/retitle MULTIARCH-6023: Update CI schedule: run 5.0 builds on weekdays and 4.23 builds every Saturday

@openshift-ci openshift-ci Bot changed the title [MULTIARCH-6023](https://redhat.atlassian.net/browse/MULTIARCH-6023): Update CI schedule: run 5.0 builds on weekdays and 4.23 builds every Saturday MULTIARCH-6023: Update CI schedule: run 5.0 builds on weekdays and 4.23 builds every Saturday Aug 10, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@raja-0940: This pull request references MULTIARCH-6023 which is a valid jira issue.

Details

In response to this:

This PR resolves the scheduling conflicts between the 4.23 and 5.0.0 CI nightly builds

Before this change:

  • Both builds were scheduled to run on odd numbered days, resulting in a schedule conflict.

After this change:

  • 4.23.0 nightly builds will run on odd- numbered days.
  • 5.0.0 nightly builds will run on even-numbered days.

Summary by CodeRabbit

  • Updated the OpenShift PowerVS OVN multi-architecture nightly job schedules.
  • The 5.0.0 build now runs at 06:00 UTC on weekdays.
  • The 4.23.0 build now runs at 06:00 UTC every Saturday.
  • These schedules prevent conflicts between the 5.0.0 and 4.23.0 builds.

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 10, 2026
@prb112

prb112 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot

openshift-ci-robot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@prb112: This pull request references MULTIARCH-6023 which is a valid jira issue.

Details

In response to this:

/jira refresh

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.

@prb112

prb112 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@prb112: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 10, 2026

@prb112 prb112 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 10, 2026
@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: prb112, raja-0940

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 10, 2026
@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@raja-0940: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 572b8d0 into openshift:main Aug 10, 2026
16 checks passed
jzding pushed a commit to jzding/release that referenced this pull request Aug 11, 2026
…Saturday (openshift#83054)

Signed-off-by: Rajakumar Battula <rbattula@redhat.com>
TimurMP pushed a commit to TimurMP/release that referenced this pull request Sep 5, 2026
…Saturday (openshift#83054)

Signed-off-by: Rajakumar Battula <rbattula@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants