When using vanilla buildkit cache export

[dull relic]

@cunning star or @subtle grove can you help me understand the purpose of this? I see our test suite uses a registry running as a local service, how would someone use this feature in the real world?

[subtle grove]

@dull relic buildkit cache export works fine as implemented, but it is very limited in that it's "dumb". It will download cache from one location, and upload it to one location. Everything gets overwritten each time. So if you use it naively, you end up caching very little. You can orchestrate it to mamke your caching smarter, but it requires very workfload-specific knowledge. So it's been relegated to a power tool for extreme power users who don't mind doing a lot of app-specific and infra-specific work.

But lately, I've been wondering - since dagger got smarter, and has more context on the workload than before, maybe we could do more of that work for the user automatically, and leverage cache export as a shortcut to get better cache distribution with less engineering effort than we thought?

My question above was related to prototyping that

[dull relic]

Thanks, all that makes sense, what did you find? I’d love to see your prototypes if they are handy