#Github actions caching

1 messages · Page 1 of 1 (latest)

pure bloom
#

Default github runners run a different VM per workflow so your Dagger cache is not persisted that way. There's multiple ways to get around that. See https://docs.dagger.io/ci/integrations/github-actions to start. @frosty karma may be able to help you figure out the best option.

GitHub Actions | Dagger

Dagger provides a GitHub Action that can be used in any GitHub Actions workflow to call one or more Dagger Functions on specific events, such as a new commit.

ripe sinew
#

thanks. I already looked into this but in the end we either have to pay "Depot" to benefit from optimizations or don't and multiply minutes on github actions by something like 3000....

low dew
# ripe sinew thanks. I already looked into this but in the end we either have to pay "Depot" ...

hey Adrien! I'd like to briefly chime here given that we recently had a similar discussion in one of the help threads here: https://discord.com/channels/707636530424053791/1378034579054792804. I'd suggest reading the thread for more context.

To directly answer your question, we don't currently support a Dagger native caching system for Github actions. We used to have an experimental distributed caching service which we have stopped for the moment as we're working on some internal re-architecting to provide a better solution soon.

Having said that and as you probably are aware, caching OCI container/image workloads in CI is not a straightforward task. Other companies which have been in this space for a while like Docker, still don't have a solid answer for this question (https://docs.docker.com/build/ci/github-actions/cache/). Since Dagger shares some of the same internals as docker build like buildkit, the method explained in the link shared before also works in Dagger in case that might be a viable solution for you.