Speed up builds by caching build_cache #66
Conversation
… CI and also make clearer to users who might want to fully reset platformio
|
Tasmota is putting the build cache inside the main source code folder, maybe that will work for us? |
But it's also in their .gitignore so will have same impact from a CI perspective. Might make more sense as location though for local dev. Just if I change would then need to add a third cache for CI unless I override with runtime arg to put it back where I've moved it to now |
|
Not perfect, but better than it was before so tempted to merge this and can always optimise later |
|
FYI I've put mine to a scratch drive using softlink on the disk. Works well, but I do occasionally prune it. |
This is about the behaviour of CI, not regular local Dev. All filepaths are persistent locally unless they map to ramdisk or similar |
@netmindz is this change good for both local dev and ci builds? If yes let's merge. |
|
Yeah works locally as well |
Caching of ~/.platformio broken as cache key does not reference the right file, so have state cache that doesn't get updates
Build cache is outside of the ~/.platformio directory, so all the code, including libraries being rebuild for every environment every build