Your build cache is gone. Here's the fastest way back.

FosterStack is a self-hosted remote build cache, compatible with Gradle's documented HttpBuildCache protocol — the same protocol the Build Cache Node spoke. No data migration needed: a build cache is disposable by design, so an empty cache on day one just means your next build repopulates it, same as any cold cache.

Migrate now

1. Stand up FosterStack Cache in place of the Build Cache Node container:

   docker run -d -p 8080:8080 -v fscache-data:/data ghcr.io/fosterstack/cache:latest

2. Update your Gradle config — only the URL changes, the protocol is identical:

   buildCache {
       remote<HttpBuildCache> {
           url = uri("https://your-new-fosterstack-cache-url/")
           isPush = true
       }
   }

3. Confirm it's working: ./gradlew clean build --build-cache and look for FROM-CACHE in the task summary on your second build.

Full walkthrough, systemd/bare-binary option, and verification commands: github.com/fosterstack/cache/docs/migrate-from-bcn.md.

Why this is happening now, not a surprise

Gradle Inc. announced the Build Cache Node's deprecation with an EOL date of December 31, 2026, pushing users toward a commercial Develocity subscription. Removing the image early converts a soft deadline into a hard break — which is what you're seeing if you landed here from a failed build.

Verify what you're running

Every FosterStack Cache release is signed keylessly and carries a SLSA provenance attestation — see verify our images for the exact commands, copy-pasteable.

Questions, or need help migrating a larger fleet?