anchor.diff:  === Composite builds
   
   When using the configuration cache on a <<composite_builds#composite_builds,composite build>> a problem will be reported.
  -If you <<configuration_cache#ignore_problems,ignore problems>> then the included builds will be skipped when reusing the configuration cache.
  +If you <<configuration_cache#config_cache:usage:ignore_problems,ignore problems>> then the included builds will be skipped when reusing the configuration cache.
   
   See link:{gradle-issues}13503[gradle/gradle#13503].
   
  
positive.code: The Gradle TestKit (a.k.a. just TestKit) is a library that aids in testing Gradle plugins and build logic generally.
  For general guidance on how to use TestKit, see the <<test_kit.adoc#test_kit,dedicated chapter>>.
  
  To enable configuration caching in your tests, you can pass the `--configuration-cache` argument to link:{javadocPath}/org/gradle/testkit/runner/GradleRunner.html[GradleRunner] or use one of the other methods described in <<configuration_cache.adoc#enable,Enabling the configuration cache>>.
  
  You need to run your tasks twice.
  Once to prime the configuration cache.
  
negative.code: org.gradle.unsafe.configuration-cache.max-problems=5
  ----
  
  [[config_cache:usage:invalidate]]
  === Invalidating the cache
  
  The configuration cache is automatically invalidated when inputs to the configuration phase change.
  But, you may have to manually invalidate the configuration cache when untracked inputs to the configuration phase change.
  This can happen if you <<configuration_cache#config_cache:usage:ignore_problems,ignored problems>>, or when your build uses <<dynamic_versions#sec:dynamic_versions_and_changing_modules, dynamic dependency versions>> and remote dependencies changed for example.
  See the <<configuration_cache#config_cache:requirements>> and <<configuration_cache#config_cache:not_yet_implemented>> sections below for more information.
  
  The configuration cache state is stored on disk in a directory named `.gradle/configuration-cache` in the root directory of the Gradle build in use.
  