Configuration to skip task input hashing

(Robbie deMuth) #1

I’m currently trying update the infrastructure in a legacy project I’m working on to execute the Java tests via Gradle instead of Ant. The tests are integration tests that require a service to first be running on the host machine. Unfortunately, the tests need access to some files on the classpath that are used by the service. When running the combination on Windows, the Gradle build fails because Gradle attempts to acquire a lock on the files in the classpath when hashing the Test task’s inputs:

FAILURE: Build failed with an exception.

* What went wrong:
Failed to capture snapshot of input files for task ':test' property 'classpath' during up-to-date check.
> Failed to create MD5 hash for file content.

Are there any command-line options or task configurations I can use to prevent Gradle from attempting to hash the task inputs? I know the hash is used when analyzing task history, checking up-to-dateness, and interacting with the build cache, but if I’d be fine settling with always running this particular task, is there any way to skip calculating the hash?