What I've learned about repeated build work as I took BoringCache from simple save and restore APIs you could use anywhere to build-tool integrations and caching inside Docker.
Since March, I've benchmarked BoringCache on PostHog, Zed and Deno as their code changes. Here's where it makes builds faster, where another cache is level or faster, and how much data, egress and runner size it saves.
When BuildKit has to run a step again, portable cache mounts and native tool caches can preserve cached directories and tool results for reuse inside that step.
I thought Rust build cache meant the target directory. Building the BoringCache CLI taught me why dependency state, Cargo target state, and sccache solve different parts of the build.