From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I see <https://github.com/gradle/gradle/issues/20673> ("Introduce mechanism to silence/ignore specific configuration caching problems") which would help in this scenario

I'm trying to make partial config cache compatibility safe for devs to use for the scenarios that have been fully corrected while we continue working with 2nd/3rd party plugin authors to correct remaining issues.

&gt;  Is there any mode of operation where config cache issues are detected and reported but do not cause the build to fail nor cause the invalid cache entry to be written to disk?
That’s the purpose of `notCompatibleWithConfigurationCache`
<https://docs.gradle.org/current/userguide/configuration_cache.html#config_cache:task_opt_out>

I was hoping for something which didn't require comprehensive evaluation of the build logic ahead of time.  Updating all of the involved plugins to flag the tasks as incompatible (or trying to do the same from tasks.withType / tasks.named etc) requires a lot of evaluation before we can release that which we know works.

I see. That’s a capability we’re currently lacking.