nonCacheabilityCategory

The category of the non-cacheability reason: * build_cache_not_enabled - Caching is not enabled for the build * cache-if_condition_not_matched - Caching is disabled for the task via org.gradle.api.tasks.TaskOutputs#cacheIf * disabled_to_ensure_correctness - The task failed validation. Available since Gradle 7.0 * do-not-cache-if_condition_matched - Caching is disabled for the task via org.gradle.api.tasks.TaskOutputs#doNotCacheIf * multiple_outputs_declared - The task declares multiple outputs * no_outputs_declared - The task has no outputs declared * non_cacheable_inputs - One of the task inputs is not cacheable, either because some type used as an input to the task is loaded via a custom classloader, or a Java lambda is used as an input. Available since Gradle 5.0 and before Gradle 7.5 * non_cacheable_task_action - One of the task actions is not cacheable, either because it is loaded via a custom classloader, or a Java lambda is used to implement it. Available since Gradle 5.0 and before Gradle 7.5 * non_cacheable_task_implementation - The task implementation is not cacheable, either because it is loaded via a custom classloader, or a Java lambda is used to implement it. Available since Gradle 5.0 and before Gradle 7.5 * non_cacheable_tree_output - The task has a org.gradle.api.file.FileTree or a org.gradle.api.internal.file.collections.DirectoryFileTree as an output. Available since Gradle 5.0 * overlapping_outputs - The tasks outputs overlaps with another task. As Gradle cannot safely determine which task each output file belongs to, it disables caching * task_has_no_actions - The task does not declare any actions * task_output_caching_not_enabled - Caching is not enabled for the task * unknown - Reason for disabled caching is not known null when the task is cacheable or if the information is not available.