This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
Increase goreleaser timeout #778
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kolesnikovae
force-pushed
the
chore/increase-weekly-release-job-timeout
branch
from
9d2a988
to
fa53ce3
Compare
kolesnikovae
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On average, the release process takes a little over half an hour (see https://github.com/grafana/phlare/actions/workflows/weekly-release.yml), and the default goreleaser timeout is 30m.
I think it makes sense to increase goreleaser timeout to 60m. Long term we should try to decrease the job duration.