Hi 👋 In my team we are running the gradle validation scripts GHA action every week to detect cacheability issues. However I just noticed that this is not failing when there are tasks executed in the second run, so this is not helping to detect any regression automatically. In the maven action there is a

failIfNotFullyCacheable

parameter doesn't exist in the gradle one. Am I missing something? Is there any way to make this fail automatically or is it expected that the consumer of the action adds some custom logic querying to the export API to detect this by themselves? Thanks!

Hi @Roldan Galan. The action for experiment 1 does not have this flag because it is not verifying cacheability, but rather incremental building. If you look at the actions for experiments 2 and 3, the flag exists.

Thank Eric! I didn't notice that it was available in the others! 🤦 Is there any similar flag to make it fail if not fully incremental compilable?

No there isn't. Unfortunately, there's no way to distinguish whether a task is intentionally not up-to-date vs a task which is having issues. For cacheable tasks the distinction is that tasks marked with the

@CacheableTask

should be pulled from the cache.