Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.18] USHIFT-5274: Start using EUS repositories in CI on EUS operating systems #4464

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #4441

/assign ggiguash

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 24, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-5273

In response to this:

This is an automated cherry-pick of #4441

/assign ggiguash

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 dhensel-rh and jogeo January 24, 2025 11:36
@ggiguash
Copy link
Contributor

/test-required

@ggiguash
Copy link
Contributor

ggiguash commented Jan 25, 2025

/retitle [release-4.18] USHIFT-5274: Start using EUS repositories in CI on EUS operating systems

@openshift-ci openshift-ci bot changed the title [release-4.18] USHIFT-5273: Start using EUS repositories in CI on EUS operating systems [release-4.18] USHIFT-5274: Start using EUS repositories in CI on EUS operating systems Jan 25, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 25, 2025

@openshift-cherrypick-robot: This pull request references USHIFT-5274 which is a valid jira issue.

In response to this:

This is an automated cherry-pick of #4441

/assign ggiguash

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 Jan 25, 2025
@ggiguash
Copy link
Contributor

/test verify test-unit security

@ggiguash
Copy link
Contributor

/label backport-risk-assessed
/label cherry-pick-approved
/label jira/valid-bug
/lgtm

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. labels Jan 25, 2025
Copy link
Contributor

openshift-ci bot commented Jan 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, openshift-cherrypick-robot

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 25, 2025
Copy link
Contributor

openshift-ci bot commented Jan 25, 2025

@openshift-cherrypick-robot: all tests passed!

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 00db505 into openshift:release-4.18 Jan 25, 2025
9 checks passed
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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants