Skip to content
Gradle build cache

Reuse completed Gradle tasks in the next build.

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

How BoringCache fits your build.

Task outputs

Restore outputs when Gradle finds a matching cacheable task.

Existing task rules

Gradle keeps its cacheability decisions and input keys.

Across machines

Use one workspace in CI and local development.

Add shared storage to your Gradle workflow.

Keep your wrapper and build commands. Use the workspace to inspect reads, misses, transfers, and stored cache.

See how your Gradle cache is used.

Track cache reads, writes, transfers, and stored data across your builds.

Explore the workspace →
OpenTelemetry Java · Workspace insights
Cache hits

BoringCache · GitHub runner · 4 vCPU

96.7% of 4,722 lookups over 6 builds

Served from the runner
Under 1 ms per read
Read from cache
255 MB

Gradle benchmark

All Gradle results →

Build times grouped by runner, with cold and warm builds shown separately.

OpenTelemetry Java

Gradle

Benchmark →

OpenTelemetry API and SDK for Java.

Average restore, build and save · lower is better

GitHub runner

4 vCPU · 16 GB · Ubuntu 24.04 x86-64

BoringCache
3 min 8 s 6 builds
Depot Cache
3 min 41 s 6 builds
GHA Cache
3 min 0 s 6 builds
Same CPU model

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.

Depot Cache vs BoringCache
1.26× · 1 of 6
GHA Cache vs BoringCache
0.95× · 2 of 6
5 CPU models recorded
BoringCache · Build cache
AMD EPYC 9V74 (2 builds) · AMD EPYC 7763 (1 build) · Intel Xeon Platinum 8370C (1 build) · Intel Xeon Platinum 8573C (1 build) · AMD EPYC 9V45 (1 build)
Depot Cache
AMD EPYC 7763 (4 builds) · Intel Xeon Platinum 8573C (1 build) · AMD EPYC 9V74 (1 build)
GHA Cache · Local cache directory restored and saved by actions/cache
AMD EPYC 9V74 (6 builds)
Cold and warm builds

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.

One cold and warm build per cache
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
Cache hits

BoringCache · GitHub runner · 4 vCPU

96.7% of 4,722 lookups over 6 builds

Served from the runner
Under 1 ms per read
Read from cache
255 MB

Keep shared-cache publication in trusted jobs.

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

  • Trusted builds Publish shared cache for the next build Read + publish
  • Pull requests Restore cache without replacing it Read only
  • Local development Use a scoped credential for the workspace Scoped access

Common questions

Can we use BoringCache for Gradle remote caching?
Yes. BoringCache provides a shared endpoint for Gradle's HTTP build cache. It does not replace Develocity's broader feature set.
Can Gradle cache share the same workspace as Docker cache?
Yes. Gradle, Docker, directory caches, and other supported tools can share the same BoringCache workspace.
Read the Gradle setup guide →

Set up Gradle caching

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