Skip to content

Conversation

@tmshort
Copy link
Contributor

@tmshort tmshort commented Jun 30, 2025

Update the e2e registry Dockerfile to use golang 1.24/OCP 4.20

Update the e2e registry Dockerfile to use golang 1.24/OCP 4.20

Signed-off-by: Todd Short <todd.short@me.com>
@openshift-ci openshift-ci bot requested review from oceanc80 and thetechnick June 30, 2025 17:07
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 30, 2025
@oceanc80
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 30, 2025
@tmshort tmshort changed the title UPSTREAM: <carry>: Update e2e registry to use 1.24/4.20 NO-ISSUE: Update e2e registry to use 1.24/4.20 Jun 30, 2025
@openshift-ci-robot
Copy link

@tmshort: This pull request explicitly references no jira issue.

In response to this:

Update the e2e registry Dockerfile to use golang 1.24/OCP 4.20

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 Jun 30, 2025
Copy link
Contributor

@camilamacedo86 camilamacedo86 left a comment

Choose a reason for hiding this comment

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

/lgtm

@tmshort
Copy link
Contributor Author

tmshort commented Jun 30, 2025

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 30, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, grokspawn, oceanc80, tmshort

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

The pull request process is described here

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

@tmshort
Copy link
Contributor Author

tmshort commented Jun 30, 2025

/retest-required

1 similar comment
@tmshort
Copy link
Contributor Author

tmshort commented Jun 30, 2025

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 30, 2025

@tmshort: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 67123e6 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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 77ca9f4 into openshift:main Jun 30, 2025
9 of 10 checks passed
@tmshort tmshort deleted the registry-4.20 branch June 30, 2025 23:04
@tmshort tmshort changed the title NO-ISSUE: Update e2e registry to use 1.24/4.20 OPRUN-3990: Update e2e registry to use 1.24/4.20 Jul 3, 2025
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants