ci(release): warm the cross-compile build cache between releases - #39
Merged
Conversation
setup-go's built-in cache is exact-match on go.sum (any dependency bump means a fully cold build of every GOOS/GOARCH target) and its immutable snapshot is claimed by whichever job saves first — usually a CI test job whose GOCACHE covers only host-platform test builds. Replace it in the release job with a go-release-* scoped module+build cache: a restore-keys prefix keeps dependency bumps warm, and the post step saves after goreleaser so the snapshot carries the full cross-compile matrix. First release populates it; later ones compile incrementally.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Same release-cache pattern rolled out across the goreleaser repos (and the pinpredict
setup-gocomposite in pinpredict/.github#56): setup-go's built-in cache can't warm a goreleaser job — its key is exact-match ongo.sumand its snapshot comes from CI test jobs, which build only the host platform. Ago-release--scopedactions/cachewith a restore-keys fallback, saved after goreleaser, restores a build cache covering every cross-compiled target. First release after merge populates the cache; subsequent ones compile mostly incrementally. No release behavior changes — cache only.