Build outputs
Use the Maven Build Cache Extension's stored results.
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
permissions: contents: read id-token: write steps: - uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: mode: maven trust-policy: auto - run: ./mvnw verify
steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache maven
build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache maven
Use the Maven Build Cache Extension's stored results.
Keep the configuration that defines reusable Maven work.
Inspect reads, misses, and transfers in the workspace.
BoringCache provides the cache connection. Plugin parameters, line endings, and the build environment still determine whether stored results are compatible.
Track cache reads, writes, transfers, and stored data across your builds.
Explore the workspace →BoringCache · GitHub runner · 4 vCPU
74.9% of 6,472 lookups over 17 builds
Build times grouped by runner, with cold and warm builds shown separately.
Maven
Benchmark →Spring framework modules for AI applications.
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 | 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 |
BoringCache · GitHub runner · 4 vCPU
74.9% of 6,472 lookups over 17 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 maven
We use cookies to understand how people use BoringCache. Privacy policy