Skip to content
Maven build cache

Reuse Maven outputs beyond a single runner.

Connect the Maven Build Cache Extension to shared storage. Let another compatible build reuse results while Maven keeps its own cache records and rules.

.boringcache.toml
workspace = "my-org/app"

[adapters.maven]
tag = "maven-cache"
command = ["./mvnw", "verify"]
boringcache maven

How BoringCache fits your build.

Build outputs

Use the Maven Build Cache Extension's stored results.

Your project settings

Keep the configuration that defines reusable Maven work.

Shared visibility

Inspect reads, misses, and transfers in the workspace.

Keep Maven in charge of the build.

BoringCache provides the cache connection. Plugin parameters, line endings, and the build environment still determine whether stored results are compatible.

See how your Maven cache is used.

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

Explore the workspace →
Spring AI · Workspace insights
Cache hits

BoringCache · GitHub runner · 4 vCPU

74.9% of 6,472 lookups over 17 builds

Served from the runner
Under 1 ms per read
Read from cache
1.88 GB

Maven benchmark

All Maven results →

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

Spring AI

Maven

Benchmark →

Spring framework modules for AI applications.

Average restore, build and save · lower is better

GitHub runner

4 vCPU · 16 GB · Ubuntu 24.04 x86-64

BoringCache
4 min 2 s 17 builds
Depot Cache
5 min 37 s 17 builds
GHA Cache
4 min 15 s 17 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.30× · 7 of 17
GHA Cache vs BoringCache
0.99× · 4 of 17
5 CPU models recorded
BoringCache · Build cache
AMD EPYC 7763 (8 builds) · AMD EPYC 9V45 (5 builds) · Intel Xeon Platinum 8573C (3 builds) · AMD EPYC 9V74 (1 build)
Depot Cache
AMD EPYC 7763 (11 builds) · AMD EPYC 9V74 (4 builds) · Intel Xeon Platinum 8573C (1 build) · AMD EPYC 9V45 (1 build)
GHA Cache · Local cache directory restored and saved by actions/cache
AMD EPYC 7763 (9 builds) · AMD EPYC 9V45 (5 builds) · AMD EPYC 9V74 (2 builds) · Intel Xeon 6973P-C (1 build)
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 8 min 23 s 42.0 s Cold: AMD EPYC 7763 · Warm: Intel Xeon Platinum 8370C
Depot Cache 10 min 58 s 3 min 23 s AMD EPYC 9V74 Different CPU
GHA Cache Local cache directory restored and saved by actions/cache 8 min 16 s 8 min 2 s AMD EPYC 7763 Different CPU
Cache hits

BoringCache · GitHub runner · 4 vCPU

74.9% of 6,472 lookups over 17 builds

Served from the runner
Under 1 ms per read
Read from cache
1.88 GB

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

Does Maven cache always hit across local and CI?
No. Maven cache portability depends on line endings, plugin parameters, environment, and project configuration.
Does BoringCache require replacing Maven?
No. Maven still runs normally. BoringCache provides the shared cache endpoint and workspace controls.
Can Maven and Gradle use the same BoringCache workspace?
Yes. Each tool keeps its own protocol while sharing workspace access and reporting.
Read the Maven setup guide →

Set up Maven 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 maven