Skip to content

[release-4.18] USHIFT-6365: Mirror test assets images in local registry#5873

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.18from
ggiguash:mirror-test-assets-418
Dec 8, 2025
Merged

[release-4.18] USHIFT-6365: Mirror test assets images in local registry#5873
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.18from
ggiguash:mirror-test-assets-418

Conversation

@ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Dec 8, 2025

Manual cherry-pick of #5863

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 8, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 8, 2025

@ggiguash: This pull request references USHIFT-6365 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 bug to target either version "4.18." or "openshift-4.18.", but it targets "openshift-4.21" instead.

Details

In response to this:

Manual cherry-pick of #5863

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 openshift-ci bot requested review from agullon and jogeo December 8, 2025 06:28
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 8, 2025
@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 8, 2025

/test e2e-aws-tests-bootc-periodic

@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 8, 2025

/test e2e-aws-tests-bootc-periodic e2e-aws-tests-periodic

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 8, 2025

@ggiguash: 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.

@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 8, 2025

/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 8, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 8, 2025
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

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.

@pmtk
Copy link
Member

pmtk commented Dec 8, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 8, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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-merge-bot openshift-merge-bot bot merged commit 84a4641 into openshift:release-4.18 Dec 8, 2025
13 checks passed
@ggiguash ggiguash deleted the mirror-test-assets-418 branch December 9, 2025 06:26
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants