Thanks NobbZ
I opened this issue on the rebar3 repo: How to cache build files on CI? · Issue #1824 · erlang/rebar3 · GitHub
samphilipd
axelson
Scenic Core Team
OvermindDL1
I ‘think’ if you just touch every compiled/beam file then it won’t recompile them due to how rebar works? I ‘think’? >.>
0
kelvinst
I tried:
touch _build/test/lib/*/ebin/*
touch _build/test/lib/*/.mix/*
touch _build/test/lib/*/include/*
touch _build/test/lib/*/consolidated/*
touch _build/test/lib/*/mix.rebar.config
Still recompiles everything, not sure if those are the files and if someone were able to solve. @axelson, did you found out?
1
axelson
Scenic Core Team
We don’t currently have any direct erlang dependencies so unfortunately I’m not that much help at the moment.
0
kelvinst
Qqwy
TypeCheck Core Team
Related: Are there people that have experience in doing the same thing (caching Elixir and/or Erlang dependencies so that only changed things are re-compiled) for the Travis CI?
Currently the Travis builds take almost four minutes, of which running the actual test suite takes only about 15 seconds.
0
idi527
Just ran into a somewhat similar issue (erlang deps didn’t seem to be cached) and in my case the problem was in not caching deps folder after running mix compile. This is important since rebar3 actually stores ebins in deps, and in _build mix only creates symlinks.
So, my approach before (which had the same problem as in OP):
# deps stage
- cache pull deps
- mix deps.get
- cache push deps
# compile stage
- cache pull deps, _build
- mix compile
- cache push _build
and my approach now:
# deps stage
- cache pull deps
- mix deps.get
- cache push deps
# compile stage
- cache pull deps, _build
- mix compile
- cache push deps, _build # <-- !!!
4
axelson
Scenic Core Team