Hi everybody, before configuration cache was enabled on my project, Gradle never executed tests if there were no changes to the code. After I enabled the configuration cache, now all tests and "checkstyle" tasks are executed every time. Does configuration cache changes something in that regard? (I also always had org.gradle.caching=true)

It shouldn't. And

org.gradle.caching

should not be relevant either, it just controls whether results are stored to cane and can be taken from there if inputs are the same. Run with

--info

, then you should be told why a task is considered out of date

@Vampire thanks for the hint. It is the

build-info.properties

that is updated by the Spring Boot plugin with the time the build. Is it possible to tell Gradle that this file should not affect the task cache?

That shouldn't be influenced by configuration cache though

Thanks! I found the solution. And yes, it has nothing to do with configuration cache. Just a coincidence.

Did you have a look at the link I sent? 😉

yes, it gave me the idea

The idea? The example in that docs is exactly your case. 😄

I had some misunderstandings on my side