anchor.diff:  When using a shared build cache for task output caching this even works across developer machines and build agents.
   
   Apart from task output caching, we expect other features to use the build cache in the future.
  +
  +NOTE: A complete guide is available about https://guides.gradle.org/using-build-cache/[using the build cache]. It covers the different scenarios caching can improve, and detailed discussions of the different caveats you need to be aware of when enabling caching for a build.
   
   [[sec:build_cache_enable]]
   === Enable the Build Cache
  
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.
  