3 ms·
It's also slow and difficult to cache build artifacts which makes it immensely painful to debug if you have anything of moderate complexity. Allegedly there's
by unlinked_dll 7y ago
It's also slow and difficult to cache build artifacts which makes it immensely painful to debug if you have anything of moderate complexity.
Allegedly there's a way to cache image layers and artifacts on Github. I've taken to pushing them to S3 buckets so my CI runs can be incremental where possible.
- gitgud 7y agoIt's fairly easy to cache folders in Github actions, we use it for node_modules, the refreshed when the package.json file changes. See [1] actions/cache for more details. [1] https://github.com/actions/cache https://github.com/actions/cache
- unlinked_dll 7y agoHow does this work for build artifacts generated by a docker image? I looked at it awhile back but it didn't fit my use cases.