Skip to content

[release-4.14] USHIFT-2463: Add PreRunModifier flag to skip RF#3514

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
agullon:skip_rf_tests-4.14
Jun 20, 2024
Merged

[release-4.14] USHIFT-2463: Add PreRunModifier flag to skip RF#3514
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
agullon:skip_rf_tests-4.14

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Jun 19, 2024

Manual cherry-pick from #3343

@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 19, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 19, 2024

@agullon: This pull request references USHIFT-2463 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 either version "4.14." or "openshift-4.14.", but it targets "openshift-4.16" instead.

Details

In response to this:

Manual cherry-pick from #3343

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 copejon and ggiguash June 19, 2024 08:40
@agullon
Copy link
Contributor Author

agullon commented Jun 19, 2024

/retest

1 similar comment
@agullon
Copy link
Contributor Author

agullon commented Jun 19, 2024

/retest

@copejon
Copy link
Contributor

copejon commented Jun 19, 2024

/backport-risk-assessed
/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 19, 2024
@ggiguash
Copy link
Contributor

/label backport-risk-assessed
/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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 20, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, copejon, ggiguash

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

@agullon
Copy link
Contributor Author

agullon commented Jun 20, 2024

/label cherry-pick-approved

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 20, 2024

@agullon: Can not set label cherry-pick-approved: Must be member in one of these teams: []

Details

In response to this:

/label cherry-pick-approved

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.

@pacevedom
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 20, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 20, 2024

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

@openshift-merge-bot openshift-merge-bot bot merged commit f6744fa into openshift:release-4.14 Jun 20, 2024
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.

5 participants