Still, tasks in the same project are not allowed to execute in parallel unless they are specifically written to do so.

Running tasks in parallel using the –parallel flag already improves build time. In Gradle 8.1 the configuration cache will be stable. This is an opt-in feature in Gradle 8.0 that saves people significant time. The configuration phase only needs to run if there is a change in how the project is configured. This reduces the cost of the configuration phase by caching the result and reusing this for subsequent builds. To improve this situation, the experimental feature called configuration cache was introduced in version 6.6. Without the configuration cache the configuration phase needs to be repeated even if there is no change to the configuration. Many performance features focus on the execution phase however, the configuration phase can be time-consuming.

With every Gradle release, the goal is to improve performance, ensuring that each iteration surpasses its predecessor.Ĭonfiguration cache Faster configuration timeĮvery Gradle build has a lifecycle: initialization, configuration, and execution. Slow builds can have detrimental effects and that shipping faster and more frequently is important, especially for larger companies like Square. If you want to stay up-to-date with new Gradle features and other developments, subscribe to our newsletter and follow us on Twitter or Mastodon. Upgrade now to try them with your build or start a new project with Gradle. The major improvements since Gradle 7.0 are organized into the following categories: Following the release of Gradle 7.0 in May 2021, we’ve dedicated ourselves to streamlining usability so that performing common tasks is effortless, enabling you to concentrate on maximizing productivity. Gradle 8.0 marks the next major milestone in Gradle’s ongoing mission to revolutionize build automation and enhance developer productivity.

Gradle build system