Gradle 6.6 introduces an experimental configuration caching feature that skips the configuration phase on subsequent builds when nothing affecting build configuration has changed. By caching the task graph state, builds can run faster with more parallelism and cached dependency resolution. Benchmarks show dramatic improvements: a large Java build with ~500 subprojects saw `assemble` drop from ~40s to ~13s, and a large Android build with ~2500 subprojects saw `:help` go from ~25s to ~0.5s. The feature is opt-in via `--configuration-cache` flag or a `gradle.properties` entry. Plugins must meet specific requirements to be compatible, and many including some core Gradle plugins are not yet fully compliant. An HTML report helps diagnose compatibility issues.
Table of contents
Table of ContentsIntroductionConfiguration caching in action #Build time improvements #How does it work? #Requirements and limitations #Try out configuration caching #DiscussSort: