OKD-388: Add ci-operator config for OKD SCOS 4.22 CoreOS image - #82269
Conversation
|
@pskrbasu: This pull request references OKD-388 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 task to target the "5.0.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. |
|
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 (2)
📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
WalkthroughAdds a release-4.22 OKD SCOS CI configuration with image builds, promotion, resource settings, testing, and metadata. Updates the master OKD SCOS configuration to promote and integrate ChangesOKD SCOS CI configuration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
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 |
|
/pj-rehearse pull-ci-openshift-os-release-4.22-okd-scos-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-os-release-4.22-okd-scos-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
| - build_args: | ||
| - name: OPENSHIFT_CI | ||
| value: "1" | ||
| dockerfile_path: extensions/Containerfile |
There was a problem hiding this comment.
i changed this to Containerfile. @pskrbasu can you run make jobs to update the pre and postsubmit jobs?
|
/pj-rehearse pull-ci-openshift-os-release-4.22-okd-scos-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Add dedicated ci-operator config for the release-4.22 branch of openshift/os (OKD SCOS variant) and remove scos-4.22 promotion targets from the master branch config so that 4.22 and 5.0 CoreOS image builds are independent.
595dded to
c4486b9
Compare
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@pskrbasu: 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: pskrbasu 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 |
…hift#82269) Add dedicated ci-operator config for the release-4.22 branch of openshift/os (OKD SCOS variant) and remove scos-4.22 promotion targets from the master branch config so that 4.22 and 5.0 CoreOS image builds are independent.
…hift#82269) Add dedicated ci-operator config for the release-4.22 branch of openshift/os (OKD SCOS variant) and remove scos-4.22 promotion targets from the master branch config so that 4.22 and 5.0 CoreOS image builds are independent.
Summary
release-4.22branch ofopenshift/os(OKD SCOS variant), modeled on the existing 4.21 configscos-4.22/scos-4.22-artpromotion targets from themasterbranch config and update integration reference toscos-5.0, so 4.22 and 5.0 CoreOS image builds are independentSummary by CodeRabbit
ci-operatorconfig foropenshift/osokd-scoson therelease-4.22branch to build the CoreOS assembler and extensions, promote them toorigin(scos-4.22andscos-4.22-art), and include built images inreleases.latest.integration; also defines optionale2e-aws-ovnusing theopenshift-e2e-awsworkflow.openshift/osmasterokd-scosconfig to integrate/promotescos-5.0images instead (removing the priorscos-4.22/scos-4.22-artpromotion targets and switchingreleases.latest.integrationtoscos-5.0), separating the 4.22 and 5.0 CoreOS image build streams.OKD-388;openshift-ci-robotnoted it has no target version configured even though the expected target branch/version is5.0.0, and requested rehearsals for thepull-ci-openshift-os-release-4.22-okd-scos-imagesjob twice.