Skip to content

[release-4.14] USHIFT-3268: Increase cncf result collection timeout to 10m#3416

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
openshift-cherrypick-robot:cherry-pick-3414-to-release-4.14
May 31, 2024
Merged

[release-4.14] USHIFT-3268: Increase cncf result collection timeout to 10m#3416
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
openshift-cherrypick-robot:cherry-pick-3414-to-release-4.14

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #3414

/assign ggiguash

@openshift-ci-robot
Copy link

openshift-ci-robot commented May 30, 2024

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

Details

In response to this:

This is an automated cherry-pick of #3414

/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 copejon and ggiguash May 30, 2024 17:13
@ggiguash
Copy link
Contributor

/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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 May 30, 2024
@ggiguash
Copy link
Contributor

/label cherry-pick-approved
/label jira/valid-bug

@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 May 30, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 30, 2024

@openshift-cherrypick-robot: 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.

@copejon
Copy link
Contributor

copejon commented May 30, 2024

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 30, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@ggiguash
Copy link
Contributor

/label jira/valid-bug

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label May 31, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit f52ff84 into openshift:release-4.14 May 31, 2024
@ggiguash
Copy link
Contributor

ggiguash commented May 31, 2024

/retitle [release-4.14] USHIFT-3268: Increase cncf result collection timeout to 10m

@openshift-ci openshift-ci bot changed the title [release-4.14] USHIFT-3267: Increase cncf result collection timeout to 10m [release-4.14] USHIFT-3268: Increase cncf result collection timeout to 10m May 31, 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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants