Over a million developers have joined DZone.

Gradle Goodness: Enable Build Cache for All Builds [Snippet]

DZone's Guide to

Gradle Goodness: Enable Build Cache for All Builds [Snippet]

In this short post, we take a look at a recent feature of Gradle: the build cache. This customizable tool can be a real time-saver, particularly for CI.

· Java Zone ·
Free Resource

Bring content to any platform with the open-source BloomReach CMS. Try for free.

Gradle 3.5 introduced the build cache. With the build cache, we can share task output between builds on different computers. For example, the build output from a continuous integration server can be used on a developer's computer. To use the build cache feature, we use the command-line option --build-cache.

Instead of using the command-line option --build-cache, we can set the Gradle property org.gradle.caching with the value true in the file gradle.properties of our project. To set this property for all our projects, we set the property in the gradle.properties file in the Gradle home directory, which is usually at USER_HOME/.gradle/gradle.properties.

In the following example, we set the property org.gradle.caching in ~/.gradle/gradle.properties:

# File: ~/.gradle/gradle.properties

If we want to disable the build cache feature set via the global property, we can use the command-line option --no-build-cache to disable the build cache for a particular build.

Written with Gradle 3.5.

BloomReach CMS: the API-first CMS of the future. Open-source & enterprise-grade. - As a Java developer, you will feel at home using Maven builds and your favorite IDE (e.g. Eclipse or IntelliJ) and continuous integration server (e.g. Jenkins). Manage your Java objects using Spring Framework, write your templates in JSP or Freemarker. Try for free.

gradle ,java ,groovy ,build cache

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}