/ Gradle Build Tool

Introducing the DS Gradle Cloud Cache

One of the prominent features of using Gradle is the ability to seamlessly cache the artifacts of a build to provide a significant performance boost to the build. This is what sets the Gradle apart from other build systems like Maven or Ant.

While Gradle itself comes with a cache available to run on your local machine, or a docker container you can run in your local network to improve the builds, we feel that it is not yet enough.

So we are now introducing the DS Gradle Cloud Cache powered by Amazon S3.

DS Gradle Cloud cache

The DS Gradle Cloud Cache integrates into your Gradle build seamlessly and supports any project type. Weather you are building Java, C or Javascript projects, if your project is viable for caching, the DS Gradle Cloud Cache will work out of the box.

All official Gradle plugins as well as Devsoap plugins are highly optimized for caching so for best results you will get by combining those in your build.

On the contrary to the local caching methods mentioned above, the DS Gradle Cloud Cache uses Amazon S3 for object storage. This object storage is fully sponsored by Devsoap so you don't need to concern yourself with setting up an AWS account or configuring the AWS integration. The stability and performance of S3 is undeniable and even sharing cached objects with your teammates on the other side of the globe shouldn't be an issue.

One of the key aspects when designing the cache was to make it simple to use. In your Gradle build you only need to add the following to your settings.gradle file:


// 1. Add the plugin
  plugins {
      id "com.devsoap.cache" version "1.0.2"

  // 2. Assign your license details
  devsoap {
      email = '...'
      key = '...'
  // Optional: Disable local build cache
  buildCache {
     local {
         enabled = false

If you already have purchased a subscription for another Devsoap product you can use those credentials. The cache is included in every subscription for free! If you don't yet have a subscription you can get one here.

And that is it! There is no other configuration needed besides the above. No extra tasks to run. The cache configuration is fully transparent. The next time you run your gradle build with --build-cache your project cache artifacts will be uploaded to the distributed cache.

The cache will hold your artifacts for one week (1 week retention policy) but you can at any time update the artifacts to keep them in the cache.

So why not take the cache into use **today?

** The product is only available for beta testers. If you want to participate please send an email to hello@devsoap.com.