Action results
Reuse work for actions with matching inputs.
Share action results and output files between CI and developer machines. Matching actions can read the completed result instead of executing again.
.boringcache.toml
workspace = "my-org/app" [adapters.bazel] tag = "bazel-cache" command = ["bazel", "build", "//..."]
boringcache bazel
permissions: contents: read id-token: write steps: - uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: mode: bazel trust-policy: auto - run: bazel build //...
steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache bazel
build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache bazel
Reuse work for actions with matching inputs.
Make the associated build outputs available to another machine.
Keep the targets, dependencies, and cache keys Bazel already computes.
BoringCache supplies the HTTP cache endpoint and workspace access. Bazel retains control of action identity and execution.
BoringCache manages remote cache storage and workspace access. Keep Bazel's targets and existing runners. A matching action can retrieve its result and outputs; a miss still executes on your machine.
Use the HTTP adapter for Bazel's HTTP cache interface, or the REAPI adapter for its gRPC cache interface. Both provide caching. Neither moves action execution to a remote worker.
Publish from a trusted build, then build the same targets at the same commit from a fresh checkout with restore access. Compare remote cache hits and total build time. A second build on the original runner may reuse local outputs instead.
If actions miss, compare their inputs, toolchain, flags, and environment. Matching source alone does not guarantee matching action keys.
Bazel's remote-cache troubleshooting →Inspect action-cache hits, misses, and transferred outputs for each run.
Explore the workspace →BoringCache · GitHub runner · 4 vCPU
99.5% of 82,319 lookups over 9 builds
Build times grouped by runner, with cold and warm builds shown separately.
Bazel
Benchmark →RPC framework. The C++ library and its CSM greeter client and server, built with Bazel.
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Builds of one commit can land on different CPU models. These ratios use only the build pairs where both caches ran on the same model; above 1.00× means BoringCache's total time over those pairs was lower.
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| BoringCache Remote cache | 28 min 3 s | 1 min 46 s | Cold: Intel Xeon 6973P-C · Warm: AMD EPYC 7763 |
| BuildBuddy | 26 min 52 s | 1 min 51 s | AMD EPYC 9V45 Different CPU |
| Depot Cache | 54 min 20 s | 2 min 26 s | Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V74 Different CPU |
| GHA Cache Bazel --disk_cache restored and saved by actions/cache | 27 min 2 s | 73.7 s | Cold: Intel Xeon 6973P-C · Warm: Intel Xeon Platinum 8573C Different CPU |
| NativeLink NativeLink server on the runner | 26 min 6 s | 11 min 35 s | Cold: AMD EPYC 9V45 · Warm: AMD EPYC 7763 Different CPU |
BoringCache · GitHub runner · 4 vCPU
99.5% of 82,319 lookups over 9 builds
Give consumers restore access and publishers a separate permission. Connect supported CI through OIDC or use scoped credentials.
Connect your CI →Separate readers and publishers
Install the CLI. Run onboarding to connect your repository and configure your cache.
30-day trial. No credit card required.
curl -sSL https://install.boringcache.com/install.sh | sh
boringcache onboard
boringcache bazel
We use cookies to understand how people use BoringCache. Privacy policy