WINC-520: Use Existing OpenShift Releases for CI jobs#31811
Conversation
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
/test ? |
|
@jrvaldes: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
DetailsIn response to this:
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. |
|
/test pj-rehearse |
jrvaldes
force-pushed
the
WINC-520-test-releases
branch
from
dea14a6 to
5e74362
Compare
|
/test pj-rehearse-more |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jrvaldes The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
jrvaldes
force-pushed
the
WINC-520-test-releases
branch
from
060cd6a to
3baa2ee
Compare
Before the CI jobs were using Ephemeral OpenShift Releases at run-time and the resulting images were bundled into the release payload being tested. With the later approach, there was a mismatch with the version of the injected oc client. This change proposes the Existing OpenShift Releases as they are intended to test software that is not part of OpenShift itself. For example, optional operators where WMCO is a valid use case. See https://docs.ci.openshift.org/docs/architecture/ci-operator/#should-i-use-an-ephemeral-or-published-release Ran: ``` make update ``` Follow-up to openshift@a692d58
jrvaldes
force-pushed
the
WINC-520-test-releases
branch
from
3baa2ee to
80a8cab
Compare
jrvaldes
changed the title
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
| name: "4.12" | ||
| namespace: ocp | ||
| candidate: | ||
| product: ocp |
There was a problem hiding this comment.
please do the same for community
|
/hold I am not sure we want to be using released OCP versions in our tests. If we want to pick up a OVN or Machine API change that is yet to be published in our e2e tests, we will have to wait for a release to happen. Unless I am misunderstanding what is meant |
openshift-ci
Bot
added
the
do-not-merge/hold
|
@jrvaldes: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@jrvaldes: Closed this PR. DetailsIn response to this:
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. |
3 participants
Before the CI jobs were using Ephemeral OpenShift Releases at run-time
and the resulting images were bundled into the release payload being
tested. With the later approach, there was a mismatch with the version of
the injected oc client.
This change proposes the Existing OpenShift Releases as they are intended
to test software that is not part of OpenShift itself. For example, optional
operators where WMCO is a valid use case. See https://docs.ci.openshift.org/docs/architecture/ci-operator/#should-i-use-an-ephemeral-or-published-release
Ran:
Follow-up to: