Compiler reuse
sccache decides whether an invocation can use a stored result.
Give Rust, C, and C++ builds access to one shared sccache store. Reuse eligible compilations from CI, containers, and local development.
.boringcache.toml
workspace = "my-org/app" [adapters.sccache] tag = "sccache-cache" command = ["cargo", "build", "--release"]
boringcache sccache
permissions: contents: read id-token: write steps: - uses: boringcache/one@f0fb9b2d926a32b10c543e92093ba00c5a291b79 # v1.33.0 with: mode: sccache trust-policy: auto - run: cargo build --release
steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache sccache
build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache sccache
sccache decides whether an invocation can use a stored result.
Matching compiler-cache data is stored once in the workspace.
Inspect compiler-cache reads, writes, and transfers.
The sccache adapter connects compiler caching to your command. For Rust builds that also need dependency and target-state reuse, use the Cargo integration.
Inspect cache hits, misses, and transfers from sccache in your workspace.
Explore the workspace →GitHub Actionsmain48b6eee
96.9%
1,834 of 1,893 sccache remote reads were hits.
95.8%
Deno · Cargo + sccache
92%
Zed · compared with actions/cache
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 GB of cache free. No credit card required.
curl -sSL https://install.boringcache.com/install.sh | sh
boringcache onboard
boringcache sccache
We use cookies to understand how people use BoringCache. Learn more