This message was deleted.

If you run with

--info

it should always tell you why a task is rerun.

Coming back to this after going through the gradle-pitest-plugin source code. It turns out some of the file inputs are using absolutePaths. Thats why the cache is kicking in for local builds but not for CI. I opened a PR - https://github.com/szpak/gradle-pitest-plugin/pull/315

I contributed to many projects and it is quite a while ago since I contributed to that one. But actually both versions, before and after look suspicious. I have no idea what these properties do and when they should cause the build to be up to date and when not. I'm not going to analyze the whole project. What I meant like suspicious is, that only the pure file path is used as textual input. Not the contents of files or directories. That's most often incorrect, but impossible to say without analysing what these properties do.