anchor.diff:  https://gradle.com/build-cache[Gradle Enterprise] includes a high-performance, easy to install and operate, shared build cache backend.
   
   [[sec:build_cache_known_issues]]
  -=== Known issues with built-in Build Caches
  -
  -The built-in build caches have some known issues which will be addressed in future releases.
  +=== Known issues with build caches backends
  +
  +The build cache backends shipped with Gradle have some known issues that will be addressed in future releases.
   
   .api:org.gradle.caching.http.HttpBuildCache[]
   |===
  
positive.code: [[build_cache]]
  == Build Cache
  
  NOTE: The build cache feature is ready to be used for Java projects. However, there are some known issues (see <<sec:task_output_caching_known_issues>> and <<sec:build_cache_known_issues>>) that you should be aware of when using it. Work continues to make this feature safer to use in any project.
  
  NOTE: The build cache feature described here is different from the http://tools.android.com/tech-docs/build-cache[Android plugin build cache].
  
  
negative.code: In order to handle volatile inputs for your tasks consider <<sec:configure_input_normalization,configuring input normalization>>.
  
  [[sec:task_output_caching_known_issues]]
  ==== Known issues with task output caching
  
  The task output caching feature has known issues that may impact the correctness of your build when using the build cache,
  and there are some caveats to keep in mind which may reduce the number of cache hits you get between machines.
  