This message was deleted.

This might be a result of some task being marked

notCompatibleWithConfigurationCache

. We have a feature request to surface such tasks in the report, but it is not there yet ( I don't have any shortcuts for finding the offending task other than grepping the build sources, or, maybe attaching a debugger and setting a breakpoint on the method.

so when any task which declares

notCompatibleWithConfigurationCache

is present in the build whole configuration cache stops working? 🤔

Not in the build, in the task graph. If the incompatible task is not to be executed, there is no reason to not use CC

That's the point. The declaration means that the task cannot be (de)serialized properly, so if such a task is present in the graph, the graph would not be serialized. You can still get configuration caching for other graphs that don't include incompatible tasks. For example, you may have CC when running

test

but not when running

deploy

if the latter task is marked as incompatible