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.17] USHIFT-4694: update common_versions.sh #4016

Open
wants to merge 2 commits into
base: release-4.17
Choose a base branch
from
Open

[release-4.17] USHIFT-4694: update common_versions.sh #4016

wants to merge 2 commits into from

Conversation

pacevedom
Copy link
Contributor

Which issue(s) this PR addresses:

Closes #

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 3, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 3, 2024 •
edited by openshift-ci bot
Loading

@pacevedom: This pull request references USHIFT-4129 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 story to target the "4.17.z" version, but no target version was set.

In response to this:

Which issue(s) this PR addresses:

Closes #

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 jogeo and pliurh October 3, 2024 08:09
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacevedom

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 Oct 3, 2024
@pacevedom
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 3, 2024
@pacevedom
Copy link
Contributor Author

/retest

@pacevedom
Copy link
Contributor Author

/test ?

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 16, 2024

@pacevedom: The following commands are available to trigger required jobs:

  • /test footprint-and-performance
  • /test images
  • /test metal-bootc-periodic-test
  • /test metal-bootc-periodic-test-arm
  • /test metal-bootc-test
  • /test metal-bootc-test-arm
  • /test metal-periodic-test
  • /test metal-periodic-test-arm
  • /test microshift-metal-cache
  • /test microshift-metal-cache-arm
  • /test microshift-metal-tests
  • /test microshift-metal-tests-arm
  • /test ocp-conformance-rhel-eus
  • /test ocp-conformance-rhel-eus-arm
  • /test ocp-full-conformance-rhel-eus
  • /test test-rpm
  • /test test-unit
  • /test verify

The following commands are available to trigger optional jobs:

  • /test test-rebase

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-microshift-release-4.17-images
  • pull-ci-openshift-microshift-release-4.17-metal-bootc-periodic-test
  • pull-ci-openshift-microshift-release-4.17-metal-bootc-periodic-test-arm
  • pull-ci-openshift-microshift-release-4.17-metal-bootc-test
  • pull-ci-openshift-microshift-release-4.17-metal-bootc-test-arm
  • pull-ci-openshift-microshift-release-4.17-metal-periodic-test
  • pull-ci-openshift-microshift-release-4.17-metal-periodic-test-arm
  • pull-ci-openshift-microshift-release-4.17-microshift-metal-tests
  • pull-ci-openshift-microshift-release-4.17-microshift-metal-tests-arm
  • pull-ci-openshift-microshift-release-4.17-test-unit
  • pull-ci-openshift-microshift-release-4.17-verify

In response to this:

/test ?

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 Author

/test all

@pacevedom pacevedom changed the title [release-4.17] USHIFT-4129: update common_versions.sh [release-4.17] USHIFT-694: update common_versions.sh Oct 16, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 16, 2024 •
edited by openshift-ci bot
Loading

@pacevedom: This pull request references USHIFT-694 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 story to target the "4.17.z" version, but no target version was set.

In response to this:

Which issue(s) this PR addresses:

Closes #

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.

@pacevedom pacevedom changed the title [release-4.17] USHIFT-694: update common_versions.sh [release-4.17] USHIFT-4694: update common_versions.sh Oct 16, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 16, 2024 •
edited by openshift-ci bot
Loading

@pacevedom: This pull request references USHIFT-4694 which is a valid jira issue.

In response to this:

Which issue(s) this PR addresses:

Closes #

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.

@pacevedom
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved

@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. labels Oct 16, 2024
@pacevedom pacevedom force-pushed the USHIFT-4129 branch 3 times, most recently from 8b5f960 to 0395cdf Compare October 17, 2024 08:50
@pacevedom
Copy link
Contributor Author

/retest

3 similar comments
@pacevedom
Copy link
Contributor Author

/retest

@pacevedom
Copy link
Contributor Author

/retest

@pacevedom
Copy link
Contributor Author

/retest

@pacevedom pacevedom force-pushed the USHIFT-4129 branch 3 times, most recently from d78eceb to 09a8523 Compare October 17, 2024 14:32
@pacevedom
Copy link
Contributor Author

/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 Oct 18, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 18, 2024

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

@pacevedom
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jogeo jogeo Awaiting requested review from jogeo

@pliurh pliurh Awaiting requested review from pliurh

Assignees
No one assigned
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.
Projects
None yet
Milestone
No milestone
Development

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