Closed Nydauron closed 1 year ago
This looks good so far, but we still need to cache go dependencies.
The fact that some tests cache now is an extremely good sign, that's almost a minute shaved off. It also means adding unit tests will be much much much faster.
It seems like the go installer does caching to, but that doesn't prevent it from downloading the mods again? There's some weird conflict going on but it does work.
Okay, so the goinstall action has issues with caching actual dependencies, and one of the recommended solutions is to do it manually instead. I'm going to try that.
Under a minute with no changes! That's pretty good. Mostly is just mongo starting now, which I'm guessing can't be cached. Still looks very promising.
Okay, so the goinstall action has issues with caching actual dependencies, and one of the recommended solutions is to do it manually instead.
Huh weird that an actions/cache
is required even though it literally says on the actions/setup-go
README that it uses actions/cache
under-the-hood.
Either way looks great!
Huh weird that an
actions/cache
is required even though it literally says on theactions/setup-go
README that it usesactions/cache
under-the-hood.Either way looks great!
I looked into it a bit more, it's because the setup-go caches only the go pkg directory, but not go's cache directory. Either way, it works, so that's good enough for me!
Adds caching to CI job to allow for faster runtime.