This message was deleted.

In your case the classpath for the

KotlinCompile

task changed (probably a change in the build logic, like buildSrc), and therefore all those complex nested properties show up as changed. You can’t see that actual value in build scans, since it only captures hashes of the inputs.

It's build from the same commit on two different machines. My local one and CI.

Which Gradle version is this on?

7.6.1

Ah, thought maybe it's https://github.com/gradle/gradle/issues/24031

The linked issue should only happen when one machine runs on Gradle 7.6 and other on Gradle 8 right? In my case both CI and my machine run on same Gradle version.

Yep, for me it happened when both machines were using Gradle 8 already (but old builds already populated the cache) so unless you ran any build with Gradle 8 then it's likely not this issue

I should probably check if the Java vendor matters since I have

jvmToolchain(17)

declared, though I understood the docs like only major version should matter (as I didn't specify vendor) https://docs.gradle.org/current/userguide/common_caching_problems.html#java_version_tracking

That's also my understanding. If you're on Kotlin Slack, here's a thread where I was asking about a very similar issue, maybe you'll find some ideas there (some people mentioned charsets and project accessors as points of interest) https://kotlinlang.slack.com/archives/C19FD9681/p1677100676448719