From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I’d say yes. I see no reason why it should not work, considering you implement the patching logic correctly (so that the result matches with non-incremental execution of the task)

how do you test an incremental task? I just learned about them, and I think I will have to migrate some tasks I have :eyes: 

Same as you test regular tasks I guess? TestKit + make changes to a test project?

Mmm but the outcome might not tell if it was incremental or not

Yeah that was the problem I was thinking about 

So you're only able to test if it worked, not if it was incremental

based on the example in the docs (println part)

You could search for a line like
```The input changes require a full rebuild for incremental task '<task path>'.```
at the INFO level Gradle logs for ensuring the task execution was incremental

<https://github.com/gradle/gradle/blob/2dcc8bc3acf59385bbb3f11010f99ad1914417bb/platforms/core-execution/execution/src/main/java/org/gradle/internal/execution/steps/ResolveInputChangesStep.java#L52|https://github.com/gradle/gradle/blob/2dcc8bc3acf59385bbb3f11010f99ad1914417bb/pla[…]rg/gradle/internal/execution/steps/ResolveInputChangesStep.java>

Another approach probably could be to print log lines from your code containing the files are actually being processed and match them with the expected ones