-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
chore(ci) : cache go-build folders #2054
Conversation
Signed-off-by: Matthieu MOREL <mmorel-35@users.noreply.github.com>
Codecov Report
@@ Coverage Diff @@
## master #2054 +/- ##
=======================================
Coverage 97.87% 97.87%
=======================================
Files 107 107
Lines 6907 6907
=======================================
Hits 6760 6760
Misses 81 81
Partials 66 66 Continue to review full report at Codecov.
|
Here's an interesting cross platform approach that uses the output of what do you think? he has it split into two separate cache steps, but I'm not sure that' necessary, since they're both using the hash of |
.github/workflows/tests.yml
Outdated
|
||
# Get values for cache paths to be used in later steps | ||
- id: go-cache | ||
run: echo "::set-output name=go-build::$(go env GOCACHE)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might as well use this approach for go env GOMODCACHE
too? I mean, it's not likely to change, but you never know and the consistency is nice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree
sweet, thanks! I'll let these latest round of tests finish running then merge. |
Signed-off-by: Matthieu MOREL mmorel-35@users.noreply.github.com