Skip to content
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

Bump goreleaser action and goreleaser itself #916

Merged
merged 1 commit into from
Jun 23, 2022

Conversation

jkremser
Copy link
Member

@jkremser jkremser commented Jun 23, 2022

hopefully fixing #904

Can't say for 100% because it's a non-deterministic issue that might be also caused by container registries (when pulling the base image), rate limiters, running on different VMs, etc. Currently the error is kinda swallowed by the goreleaser.

I ran the terratest and upgrade tests workflows (terratest.yaml & upgrade-testing.yaml) each 8 times and haven't seen any container build failures. Only once the terratests failed on this, but that's the race condition issue, not the container build thingy.

update1: well, 9 times including the build of this pr (because I rebased on master and "push-fed")
update2: haha, so the last build failed so it's not fixing the issue, but the bump can't hurt right?

Signed-off-by: Jirka Kremser [email protected]

@jkremser jkremser merged commit 8c7586b into k8gb-io:master Jun 23, 2022
@jkremser jkremser deleted the bump-goreleaser branch June 23, 2022 16:00
kuritka pushed a commit that referenced this pull request Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants