Gradle Build Cache Node Future

Help/Discuss
1

Hello,

I wanted to set up a Build Cache Node as described in the documentation. However, the Build Cache Node user manual states that it will be deprecated at the end of 2026. The accompanying release notes state that users should migrate from Build Cache Node to Develocity Edge. According to the Develocity Edge user manual, access to Develocity is required to use Develocity Edge. This was not necessary for the Build Cache Node, right?

Develocity is not an option for my hobby project. However, I would still like to look into the Remote Build Cache and used it, as it could be relevant for my work. There seem to be two options to choose from:

  • Use the deprecated Build Cache Node and hope that Develocity Edge will later also be usable without Develocity. Which seems unlikely, considering the name?
  • Use/implement own build cache server.

My question is, does Gradle plan to offer a free successor to the Gradle Build Cache Node? I couldn’t find any information on this, and it would help me make my decision.

Best regards

1 Like
2

I have no idea what Gradle folks plan, but that’s quite irrelevant.
The remote build cache “API” is quite trivial, you basically just need an HTTP server supporting GET and PUT, storing files and delivering them back.
You can for example install a free Nexus instance and use a “raw” repository as remote build cache.
This is not a theoretical statement, we do exactly that at work.

1 Like