microshift
microshift copied to clipboard
[release-4.17] USHIFT-4694: update common_versions.sh
Which issue(s) this PR addresses:
Closes #<Issue Number>
@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 #<Issue Number>
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.
/hold
/retest
/test ?
@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-imagespull-ci-openshift-microshift-release-4.17-metal-bootc-periodic-testpull-ci-openshift-microshift-release-4.17-metal-bootc-periodic-test-armpull-ci-openshift-microshift-release-4.17-metal-bootc-testpull-ci-openshift-microshift-release-4.17-metal-bootc-test-armpull-ci-openshift-microshift-release-4.17-metal-periodic-testpull-ci-openshift-microshift-release-4.17-metal-periodic-test-armpull-ci-openshift-microshift-release-4.17-microshift-metal-testspull-ci-openshift-microshift-release-4.17-microshift-metal-tests-armpull-ci-openshift-microshift-release-4.17-test-unitpull-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.
/test all
@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 #<Issue Number>
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: This pull request references USHIFT-4694 which is a valid jira issue.
In response to this:
Which issue(s) this PR addresses:
Closes #<Issue Number>
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.
/label backport-risk-assessed /label cherry-pick-approved
/retest
/retest
/retest
/retest
/label jira/valid-bug
@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.
/hold cancel
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: pacevedom, pmtk
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [pacevedom,pmtk]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment