Introducing Gradle Build Cache Beta

Gradle 3.5 introduces a build cache feature in beta that reuses task outputs locally and across machines to reduce build times. The cache works by hashing all task inputs to generate a unique key; if a matching key is found in the cache, Gradle skips task execution and copies outputs directly. Built-in tasks like JavaCompile, Test, and Checkstyle support caching out of the box. Internal Gradle CI data shows an average 25% reduction in build time per commit, with some commits seeing up to 80% improvement. A Docker-based remote cache node is available for sharing outputs between CI and developer machines. The feature is beta and not recommended for production without understanding known issues, but can be tested with the --build-cache flag or by setting org.gradle.caching=true.