benkimpel
How does mix handle partial dependency caching? (CircleCI)
CircleCI provides partial dependency caching by allowing their cache keys to match from specific to general. Let’s say most specific being a checksum of mix.lock and least specific being a branch name.
If it does not have a cache for the current mix.lock, but does have one for the branch then the restored dependencies will be partial. Does mix deps.get handle this gracefully or will it re-fetch everything?
Same question if we apply the strategy to the _build directory.
Thanks!
Most Liked
benwilson512
In my experience on Circle CI this works just fine. Here are my caching keys:
- v1-build-cache-{{ .Branch }}-{{ checksum "mix.lock" }}
- v1-build-cache-{{ .Branch }}
- v1-build-cache
The v1 bit is just a handy thing to increment incase you want to intentionally blow away the cache. I haven’t had to do that often.
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
Courses that'll move you from confusion to "Aha, now I get it!"