Closed razo7 closed 9 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: razo7
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/test ?
@mshitrit: The following commands are available to trigger required jobs:
/test 4.12-ci-index
/test 4.12-images
/test 4.12-openshift-e2e
/test 4.13-ci-index
/test 4.13-images
/test 4.13-openshift-e2e
/test 4.14-ci-index
/test 4.14-images
/test 4.14-openshift-e2e
/test 4.15-ci-index
/test 4.15-images
/test 4.15-openshift-e2e
Use /test all
to run all jobs.
/test 4.13-openshift-e2e
/test 4.15-openshift-e2e
/lgtm
/retest
/retest
/retest
Even though we use 'skipRange' for defining from which versions we can update to the version of the CSV, we also need to add the 'replace' field. It should point to the last released version and ensure that the old version isn't deleted from the index.
https://docs.engineering.redhat.com/display/CFC/Best_Practices#Best_Practices-SkipRange
Similar to https://github.com/medik8s/self-node-remediation/pull/167 and related to ECOPROJECT-1771