Backport of ci: clean GOCACHE before build into release/1.5.x #17822
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
hc-github-team-nomad-core
force-pushed
the
backport/ci-build-go-clean-cache/basically-nearby-prawn
branch
from
218a4fd to
c5c8a3e
Compare
hc-github-team-nomad-core
force-pushed
the
backport/ci-build-go-clean-cache/basically-nearby-prawn
branch
from
4e171c5 to
f16d88e
Compare
hc-github-team-nomad-core
deleted the
backport/ci-build-go-clean-cache/basically-nearby-prawn
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport
This PR is auto-generated from #17808 to be assessed for backporting due to the inclusion of the label backport/1.5.x.
The below text is copied from the body of the original PR.
This is basically to avoid Fear/Uncertainty/Doubt.
The github action actions/setup-go (and, with a different chache key, hashicorp/setup-golang) caches both GOMODCACHE (go source files), which is good, and GOCACHE (build outputs), which might be bad, if the cache was built on an OS with an older glibc than we want to support. from
go help cache:I think we've been okay so far, because the cache has always(~?) been built on 20.04 machines, but to be safe, this wipes the build cache (leaving the mod cache alone) before building.
related PR that checks the build after the fact: #17706