I am curious if it will help our builds; they are pretty slow, even to the point we have all kinds of tricks to speed them up. Thanks for trying to fix this upfront anyway.
In theory, any of the BuildKit frontends like Depot or Dagger, should be able to pass through cross-build caching from BuildKit.
This is how they all scale builds, and hopefully things become more standardized with a reduction in vendor lock in. It is surprising to me how much of the world relies on moby/buildkit, and scary if you've ever looked at the code. Primarily a single developer, not straightforward to understand, comments & docs are basically non-existent. Looks like that might be starting to change with so many companies now building and SaaS'n on top of BuildKit.
Have you tried self-hosting the runners so that you can use a beefier machine to run them on? I switched our iOS builds from Azure Pipeline's hosted runner to a rented M1 Mac Mini (from Scaleway), and our iOS build time went from 20-60 minutes (depending on how Azure was feeling that day) to a consistent 3.5 minutes.
Thank you for the comment! We have dealt with this problem throughout our own careers at multiple companies. We should support all of the tricks you may be doing to speed up your builds, but we hope you have to do fewer of them using Depot.
