-
Notifications
You must be signed in to change notification settings - Fork 48
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.
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
[release-0.85] Release v0.85.5 #1749
Conversation
Signed-off-by: GitHub <noreply@github.com>
/test pull-e2e-cnao-lifecycle-k8s-release-0.85 |
/test pull-e2e-cnao-lifecycle-k8s-release-0.85 |
it passed, basically we can delete all the releases until 0.69.0 maybe on this branch |
Those seems to come and go during deployment, maybe quay is slower, or CI machines net is slower? /retest |
Remove unsupported releases until 0.69.0 (*) 0.69.0 is also flaky. This will also cause lifecycle be shorter than 4h. * do not remove the ones that RELEASES_SELECTOR choose. There is a weird problem with RELEASES_SELECTOR, it pointed to a version that didn't exists, and still didn't fail (because it is used as an optional filter of the existing releases), for now just amended it. We can consider fixing it on a follow-up effort. Signed-off-by: Or Shoval <oshoval@redhat.com>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
/retest |
/retest not sure why it doesnt manage to deploy sometimes, we need to add post mortem in case it doesnt go away |
/test pull-e2e-cnao-multus-functests-release-0.85 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qinqon 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 |
What this PR does / why we need it:
Based on #1747
Remove unsupported releases until 0.69.0 (*)
0.69.0 is also flaky and not supported anymore.
This will also cause lifecycle be shorter than 4h.
(*) Do not remove the ones that
RELEASES_SELECTOR
choose.There is a weird problem with
RELEASES_SELECTOR
,it pointed to a version that didn't exists, and still didn't
fail (because it is used as an optional filter of the existing
releases), for now just amended it.
We can consider fixing it on a follow-up effort.
Special notes for your reviewer:
Release note: