According to docs gradle keeps track of “checksums” of task inputs / outputs to understand whether a task should execute.
However there is no explanation on when and how these checksums are calculated.
Is it possible to make gradle’s checksuming mechanism pluggable or at least more transparent?
Use case: let’s say your project tasks operate on huge amount of data as inputs and outputs. Let’s assume naively calculating md5 of files is inefficient and does not scale well. What if there is an external service that efficiently keeps track of checksums and gradle could be instructed to ask the external service for checksums of given files instead of calculating them by itself?