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

Gradle Community

This is a good question and I think it depends on what you mean by incrementality in this case since that can be an overloaded term in the Gradle world. Maybe an example of the broken "incrementality" would help here.

For the case of the `up-to-date` checking mechanism in Gradle, I can recommend the `01-validate-incremental-building.sh` script in the <https://github.com/gradle/gradle-enterprise-build-validation-scripts/blob/main/Gradle.md#structure|build validation scripts>. There isn't a way right now to make the build fail if not every task is up-to-date since there can be reasons that this is intentional. For the other scripts you can make it fail on caching errors.

For the cases of build performance regressions in incremental builds, I can recommend the <https://github.com/gradle/gradle-profiler|Gradle Profiler> and an incremental build scenario.

thanks for the pointers! I did mean `up-to-date` checks, apologies for the ambiguity :slightly_smiling_face: I’l check those scripts out. Thanks!

We run these scripts (incrementality + relocatable build cache ) regularly on CI to ensure that this features working correctly at any time

you can also use the gradle profiler and create different scenarios to make sure `up-to-date` checks are working  for expected scenarios. eg making abi vs non abi changes, etc