Hello, recently came across news that Gradle cache...
# community-support
r
Hello, recently came across news that Gradle cache nodes are deprecated and will not be available to use after end of this year docs.develocity.ai/bcn/21.2. Are there any alternatives of cache node? also do we know how can we able to get access to docs.develocity.ai/edge/2.2 or paying for the Develocity is the only option as we only use gradle cache node on CI side.. any help or suggestion will be appreciated!
m
If I understood your question correctly then there is a number of OSS remote build cache backend implementations with https://github.com/burrunan/gradle-s3-build-cache likely being the most popular one
šŸ‘€ 1
e
I saw https://github.com/chrisjenx/silo mentioned too. but honestly it should not be complex to replace
Gradle's built-in HTTP remote cache just needs a server that accepts unauthenticated or basic auth GETs and PUTs, and so if it's private to your network, you can run pretty much any HTTP server
S3 isn't straightforward because of AWS's request signing but either you point Gradle at an HTTP proxy (possibly a lambda) which does that for you, or use a plugin like burrunan/gradle-s3-build-cache which does it within Gradle
y
If you have access to S3, I would definitely recommend using the plugin that @Marcin Erdmann and @ephemient mentioned. It is pretty easy to setup on CI and the hardest part is deciding how you are going to manage the AWS keys in CI.
šŸ™Œ 1
r
Got it, yes have s3 setup in our CI so need to check
thanks guys will look into it
v
I just created a "raw" repository in our Nexus server. Works without problems as remote build cache with authentication necessary for PUT and anonymous access for GET.
r
ohh interesting, let me try nexus..
v
As others said, any HTTP server accepting PUTs and delivering the same back over GET will work With Nexus or something similar, you have some additional stuff for free, for example you can configure a LRU cleanup policy and similar.
l
Build Cache Node is officially deprecated and won't be distributed, supported, or available after December 31, 2026; Develocity 2027.1 drops support entirely and they are moving everyone to Edge (which does require a Develocity license). Alternatives: • Cloud storage plugins ā—¦ AWS S3 — burrunan/gradle-s3-build-cache — github.com/burrunan/gradle-s3-build-cache ā—¦ Google Cloud Storage — tehlers/gradle-gcs-build-cache — github.com/tehlers/gradle-gcs-build-cache ā—¦ Google Cloud Storage (fork) — alexrjones/gradle-gcs-build-cache — github.com/alexrjones/gradle-gcs-build-cache • Repository managers ā—¦ Sonatype Nexus — "raw" repository as generic HTTP cache backend ā—¦ JFrog Artifactory — generic repo as build cache — jfrog.com/help/r/jfrog-integrations-documentation/configure-gradle-to-use-build-cache • Self-hosted open-source cache servers ā—¦ Silo — chrisjenx/silo — github.com/chrisjenx/silo ā—¦ FosterStack Cache — fosterstack/cache — github.com/fosterstack/cache ā—¦ Helix Build Cache — helixframework/build-cache — github.com/helixframework/build-cache ā—¦ HTTP Gradle Cache Server — sinwe/http-gradle-cache-server — github.com/sinwe/http-gradle-cache-server