Slackbot
05/12/2022, 8:54 PMVampire
05/12/2022, 9:00 PMSam Edwards
05/12/2022, 9:03 PMorg.gradle.unsafe.configuration-cache-problems
in the project if the ~/.gradle/gradle.properties
has it set? setting it to empty doesn't have an effect, and it still fails.Vampire
05/12/2022, 9:09 PMVampire
05/12/2022, 9:11 PM~/.gradle/gradle.properties
you can only detect it and fail the build.
You can only override it via command-line in that case iirc.tony
05/12/2022, 9:11 PMVampire
05/12/2022, 9:12 PMtony
05/12/2022, 9:12 PMnotCompatible...
+ that warning is clearly incompatible. That itself ought to be considered a kind of errorVampire
05/12/2022, 9:13 PMSam Edwards
05/12/2022, 9:16 PMVampire
05/12/2022, 9:16 PMSam Edwards
05/12/2022, 9:20 PMVampire
05/12/2022, 9:23 PMThe presence of incompatible tasks in the task graph will cause the configuration state to be discarded at the end of the build unless the globaloption is set toconfiguration-cache-problems
, in which case the configuration state would still be cached in a best-effort manner as usual for the option.warn
Vampire
05/12/2022, 9:26 PMnotCompatibleWithConfigurationCache()
descriptions says
Configuration cache problems found in tasks marked incompatible will no longer cause the build to fail.And the description of
org.gradle.unsafe.configuration-cache-problems=warn
says
turn problems into warningsSo with the flag, there are no problems anymore and thus the method has no effect anymore.