🗂️ Gradle Configuration Cache

[oleg-nenashev]

In Gradle 8.1 (April 2023), we announced the general availability of the Gradle Configuration Cache. This feature significantly improves build performance by caching the result of the configuration phase and reusing this for subsequent builds. Using the configuration cache, Gradle can skip the configuration phase entirely when nothing that affects the build configuration, such as build scripts, has changed. See this blog post by Mikhail Lopatkin to learn more about how configuration caching works.

References

• Configuration Cache documentation
• Initial Announcement
• Features not implemented yet

Discuss

• #configuration-cache channel on the Community Slack
• Related GitHub Issues

Status

Planned

Beta Give feedback

1. Initial Release
2. General Availability
3. Gradle 8 - Stabilization and Improvements. See the full list here
4. Help community Gradle plugins adopt the configuration cache #13490
   @configuration-cache a:epic a:investigation in:configuration-cache in:plugin-development roadmap +6
   

   
5. Gradle 9 - Configuration cache enabled by default build-tool-roadmap#75

Considered

Beta Give feedback

1. Configuration cache should be shareable between machines #13510
   @configuration-cache a:feature in:configuration-cache +3
2. Make core Gradle plugins support the configuration cache #13454
   @configuration-cache a:epic in:configuration-cache +3
3. Configuration cache should support source dependencies #13506
   @configuration-cache a:feature in:configuration-cache in:source-dependencies +4
4. Support using third-party Java agents in TestKit with configuration cache enabled #25979
   0 of 1
   a:epic in:configuration-cache in:instrumentation in:test-kit +4
5. Gradle properties not used at configuration time can still invalidate configuration cache #20969
   a:bug in:configuration-cache +2
6. Improve configuration cache support for Java Object Serialization #13588
   @configuration-cache a:epic in:configuration-cache +3
7. Lift some execution time restrictions imposed by the configuration cache on accessing methods and variables defined in build script #22879
   @configuration-cache a:feature in:configuration-cache +3
8. Make it possible to use BuildServiceProvider as part of the configuration cache fingerprint #24085
   @configuration-cache a:feature in:build-services in:configuration-cache +4