Task outputs
Restore outputs when Gradle finds a matching cacheable task.
Connect Gradle's HTTP build cache to a shared workspace. Reuse cacheable task outputs from CI or a teammate's compatible build.
.boringcache.toml
workspace = "my-org/app" [adapters.gradle] tag = "gradle-cache" command = ["./gradlew", "build", "--build-cache"]
boringcache gradle
permissions: contents: read id-token: write steps: - uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: mode: gradle trust-policy: auto - run: ./gradlew build --build-cache
steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache gradle
build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache gradle
Restore outputs when Gradle finds a matching cacheable task.
Gradle keeps its cacheability decisions and input keys.
Use one workspace in CI and local development.
Keep your wrapper and build commands. Use the workspace to inspect reads, misses, transfers, and stored cache.
Track cache reads, writes, transfers, and stored data across your builds.
Explore the workspace →BoringCache · GitHub runner · 4 vCPU
96.7% of 4,722 lookups over 6 builds
Build times grouped by runner, with cold and warm builds shown separately.
Gradle
Benchmark →OpenTelemetry API and SDK for Java.
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 Build cache | 12 min 22 s | 2 min 8 s | AMD EPYC 9V74 |
| Depot Cache | 16 min 0 s | 2 min 36 s | Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V74 Different CPU |
| GHA Cache Local cache directory restored and saved by actions/cache | 13 min 18 s | 95.5 s | AMD EPYC 9V45 Different CPU |
BoringCache · GitHub runner · 4 vCPU
96.7% of 4,722 lookups over 6 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 gradle
We use cookies to understand how people use BoringCache. Privacy policy