-
Notifications
You must be signed in to change notification settings - Fork 7
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
Releases are broken #130
Comments
The failure is comming from operator v1 end to end tests. The release is not blocked as tag does not perform full suite at this moment. |
Does it not? From what I can cutting a tag triggers the |
This tag v2.1.16-23.3.11 technically hasn't been released. I'm under the impression that goreleaser is what turns it into an actual "release". |
It's complicated as migration tool, that is already removed, was creating artefacts to the release when tag was pushed to the repo. The release was published: https://github.com/redpanda-data/redpanda-operator/releases/tag/v2.1.16-23.3.11 For 2.1.18 and 2.1.17 we didn't have Github action run, so it didn't interrupted operator release process. |
The release pipe line is currently gummed up. We have a buildkite job that watches for new tags getting pushed. When it sees them, it will run tests and then mint a release.
Notably, it seems that only v1 tests are run for the release. That in and of itself is a bit concerning to me.
@RafalKorepta recently tagged version
v2.1.18
for release:Failures of
kuttl/harness/decommission-on-delete
are preventing anything from going out.JIRA Link: K8S-218
The text was updated successfully, but these errors were encountered: