I run my pipelines on github actions but it seems as if the github runners didnt take full advantage of dagger's caching, I've tried using the actions/cahce action to cache the .cache/dagger directory but when i run the pipeline on github it appears to be empty. Does anyone have any idea of why this might be?
#Is it possible to cache pipeline steps on Github Actions?
gleaming furnace
pastel cedar
Hey Diego!
Perfect timing, we released Dagger Cloud last week which was specifically designed to address this use case.
Whenever you run Dagger on an ephemeral environment such as your CI builder you lose some of the performance benefits of caching since there is no local storage.
The fastest and simplest way to take advantage of caching is to use Dagger Cloud which offers a globally distributed cache that just works out of the box.
You can check it out here: https://dagger.io/cloud
gleaming furnace
Thank you Lev, I really appreciate your offer; it seems like a promising solution. I'll definitely delve deeper into it for future reference. However, at this moment, I've just received the green light from my supervisor to overhaul our company's CI/CD pipelines to use Dagger. It might take a little while before I can convince them to embrace Dagger Cloud technology.
By the way, do you happen to know of any interim workaround I could implement for caching pipeline steps on GitHub Actions? From what I understand, GitHub CI runners allow for up to 10GB of cache, and I've already cached Go modules. My only concern is whether there's a way to cache pipeline steps there as well?