ROSAENG-62536: rosa-hyperfleet-api: promote CI image to ci namespace#82419
ROSAENG-62536: rosa-hyperfleet-api: promote CI image to ci namespace#82419rrp-bot wants to merge 2 commits into
Conversation
Add rosa-hyperfleet-api-ci image (built from ci/Containerfile) and a promotion block to publish it to the ci namespace. This is the first step towards switching build_root to from_repository, which requires the CI image to be pre-promoted before the switch can be made safely.
|
/ok-to-test |
openshift-ci
Bot
added
the
ok-to-test
rrp-bot
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@rrp-bot: This pull request references ROSAENG-62536 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. |
rrp-bot
added
ok-to-test
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (2)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughThe ROSA Hyperfleet API CI configuration adds explicit Dockerfile-to-repository mappings and updates image promotion to the ChangesROSA Hyperfleet image promotion
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
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 |
|
Hi @rrp-bot. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
openshift-ci
Bot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: psav, rrp-bot, typeid 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 |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse |
|
@psav: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse |
|
@psav: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@rrp-bot: The following tests failed, say
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. |
4 participants
Summary
rosa-hyperfleet-api-ciimage (built fromci/Containerfile) to the images blockpromotionblock to publishrosa-hyperfleet-api-citoregistry.ci.openshift.org/ci/rosa-hyperfleet-api-ci:latestrosa-regional-platform-apifrom CI namespace promotion (it is handled separately by the existingpush-imagepostsubmit)Why
This is the first step towards switching
build_rootfromproject_image(which runs a full Docker build on every PR, taking ~15 minutes) tofrom_repository: true. That switch requires the CI image to be pre-promoted and stable in the CI registry before it can be referenced via.ci-operator.yamlin the repo.Next steps
Once this merges and the first postsubmit promotes
rosa-hyperfleet-api-ci:latest, a follow-up PR will:build_roottofrom_repository: true+use_build_cache: true.ci-operator.yamlto therosa-hyperfleet-apirepo pointing atci/rosa-hyperfleet-api-ci:latestSummary by CodeRabbit
rosa-hyperfleet-api-ciimage to the OpenShift Online ROSA Hyperfleet API CI configuration.registry.ci.openshift.org/ci/rosa-hyperfleet-api-ci:latest.rosa-regional-platform-apiexcluded because it is promoted separately by the existing postsubmit job.