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.

Sign up for GitHub

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

Jump to bottom

[release-4.15] USHIFT-2073: Display manage_build_cache.sh output for getlast command during CI builds #2749

Merged
merged 1 commit into from
Dec 18, 2023
Merged

[release-4.15] USHIFT-2073: Display manage_build_cache.sh output for getlast command during CI builds #2749

merged 1 commit into from
Dec 18, 2023

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #2745

/assign ggiguash

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Dec 16, 2023
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 16, 2023 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: [Jira Issue USHIFT-2063](https://issues.redhat.com//browse/USHIFT-2063) has been cloned as [Jira Issue USHIFT-2073](https://issues.redhat.com//browse/USHIFT-2073). Will retitle bug to link to clone.

WARNING: Failed to update the target version for the clone. Please update the target version manually. Full error below:

Full error message. customfield_12319940 - Version name '4.15.0' is not valid: request failed. Please analyze the request body for more details. Status code: 400:
/retitle [release-4.15] [USHIFT-2073](https://issues.redhat.com//browse/USHIFT-2073): Display manage_build_cache.sh output for getlast command during CI builds

In response to this:

This is an automated cherry-pick of #2745

/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 kubernetes/test-infra repository.

@openshift-ci openshift-ci bot changed the title [release-4.15] USHIFT-2063: Display manage_build_cache.sh output for getlast command during CI builds [release-4.15] USHIFT-2073: Display manage_build_cache.sh output for getlast command during CI builds Dec 16, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 16, 2023 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: This pull request references USHIFT-2073 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.15." or "openshift-4.15.", but it targets "openshift-4.16" instead.

In response to this:

This is an automated cherry-pick of #2745

/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 kubernetes/test-infra 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 Dec 16, 2023
@ggiguash
Copy link
Contributor

/lgtm
/label backport-risk-assessed
/label jira/valid-bug

@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. lgtm Indicates that a PR is ready to be merged. labels Dec 16, 2023
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Dec 16, 2023

[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 Dec 16, 2023
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Dec 16, 2023

@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/test-infra repository. I understand the commands that are listed here.

pacevedom
pacevedom reviewed Dec 18, 2023
View reviewed changes
Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

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

/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 Dec 18, 2023
@openshift-merge-bot openshift-merge-bot bot merged commit fa18970 into openshift:release-4.15 Dec 18, 2023
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pacevedom pacevedom pacevedom left review comments

@jerpeter1 jerpeter1 Awaiting requested review from jerpeter1

@pmtk pmtk Awaiting requested review from pmtk

Assignees

@ggiguash ggiguash

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@openshift-cherrypick-robot @openshift-ci-robot @ggiguash @pacevedom