This message was deleted.
# configuration-cache
s
This message was deleted.
c
There’s a few tracked items that aren’t captured in the report (CC docs - in the “yet to be complete” section - talks about these). It’s also noted that CC is not (yet) relocatable, so you’re on the bleeding edge here.
c
I am, .. and true..I forgot about it, not even in your same laptop between 2 clones of your repository
c
yea, likely a bunch of rough edges there as not much design / development / testing has happened for CC relocation. It may still work for some use cases (it’s on the roadmap to happen at some point).
c
now that you said it.. TC folder is a hash of the VCS root.. so just changing it to use the same on both builds
c
worth a try!
c
What confused me is that the file is not shown in the report
c
Fine-grained tracking of Gradle properties as build configuration inputs
Currently, all external sources of Gradle properties (
gradle.properties
in project directories and in the
GRADLE_USER_HOME
, environment variables and system properties that set properties, and properties specified with command-line flags) are considered build configuration inputs regardless of what properties are actually used at configuration time. These sources, however, are not included in the configuration cache report.
c
but I remeber now, CC uses absolute paths
c
you can hexdump the CC file to see what is in there.
c
These sources, however, are not included in the configuration cache report.
c
hexdump -C .gradle/configuration-cache/cxma6ik32wu2e24fe7sc9dl3j/buildfingerprint.bin
😮 1
c
I've been there before..I just forgot about the issues we had 😅
c
lol 😉
c
Thanks anyway! I'll share if using the same folder fixes the issue
👍 1