Use caching in the CI pipeline #2308
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
carolynvs
added
the
playground 🙈
carolynvs
force-pushed
the
cache-go-modules
branch
2 times, most recently
from
d806eaa to
34cf1dc
Compare
carolynvs
force-pushed
the
cache-go-modules
branch
2 times, most recently
from
acf3813 to
c7031ee
Compare
Use the Azure DevOps Cache task to cache the go module directory, and the go build directory, so that go build/test run faster. I am using a separate cache key for the native go build (which is mage build) and the cross compiled binaries (which is mage xbuildall), since they generate different artifacts in the go build directory. Once a cache artifact is persisted, it can't be updated or removed. It is keyed based on our go.sumfile along with the agent OS. When we need to clear the cached artifacts, the leading version prefix should be incremented, which is used just to bust the cache. This has brought our builds down from ~6m to ~1m per job. The smoke test on Windows is still slow, but I'll address that in another PR (or most likely updating the agent image for Windows). Signed-off-by: Carolyn Van Slyck <[email protected]>
carolynvs
force-pushed
the
cache-go-modules
branch
from
c7031ee to
64a1405
Compare
carolynvs
changed the title
carolynvs
removed
the
playground 🙈
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.
Use the Azure DevOps Cache task to cache the go module directory, and the go build directory, so that go build/test run faster. I am using a separate cache key for the native go build (which is mage build) and the cross compiled binaries (which is mage xbuildall), since they generate different artifacts in the go build directory. Once a cache artifact is persisted, it can't be updated or removed. It is keyed based on our go.sum file along with the agent OS. When we need to clear the cached artifacts, the leading version prefix should be incremented, which is used just to bust the cache.
This has brought our builds down from ~6m to ~1m per job. The smoke test on Windows is still slow, but I'll address that in another PR (or most likely updating the agent image for Windows).