Anybody using GitHub Actions, Gradle 8.7 and the C...
# configuration-cache
p
Anybody using GitHub Actions, Gradle 8.7 and the CC secret? Are you able to reuse the config cache? Even when rerunning my last commit (or just adding a license file) on main causes some changed inputs, so I am curios if this feature does work for somebody...
Calculating task graph as configuration cache cannot be reused because an input to task ':build-logic:compilePluginsBlocks' has changed.
j
Have you modified a Gradle file in that commit?
p
Nope
Same when rerunning the latest commit on main.
j
Can you run a scan to see which values have changed?
p
j
configuration tab does not work with project isolation
Maybe is it related to your issue?
p
Okay, but where do you see the reason for cc miss?
In a "normal" project
j
I don’t remember if it is shown in that tab. If not, I think Gradle was creating a report file about it.
p
Yes, the cc html report, which isn't upload to the Gradle build scan.
But good idea, I will upload the report as artifact.
j
Yes, the cc html report, which isn't upload to the Gradle build scan.
Looks like a feature request
I think, I am also affected: https://github.com/gradle/actions/issues/21
j
In case you are still looking for a solution, might find it in this thread https://gradle-community.slack.com/archives/C013WEPGQF9/p1707136705820979