This message was deleted.

Is there something interesting coming?

A workaround to reuse configuration cache between machines

ooooh!

The change only improves the story on CI machines that are otherwise identical and you still need to cache basically everything. What it will allow is updating the official GitHub Gradle build action to cache configuration cache if an environment variable secret is present. Going to have to test that extensively.

@Daz DeBoer do you plan to recover configuration cache in GitHub Actions soon?

Yes, likely this year. The code to save/restore the configuration cache should be relatively easy to recover from it's prior implementation.

@Javi Silent named release: https://docs.gradle.org/8.6-milestone-1/release-notes.html

distributionUrl=https\://services.gradle.org/distributions/gradle-8.6-milestone-1-all.zip

@twisterrob have you tried it? I am getting this error

* What went wrong:
[2023-12-13 10:15:31] Could not load the value of field `parameters` of `org.gradle.api.internal.provider.DefaultValueSourceProviderFactory$DefaultObtainedValue` bean found in field `obtainedValue` of `org.gradle.configurationcache.fingerprint.ConfigurationCacheFingerprint$ValueSource` bean found in Gradle runtime.
[2023-12-13 10:15:31] > Failed to instrument class org/jetbrains/kotlin/gradle/plugin/internal/CustomPropertiesFileValueSource$Parameters in ClassLoaderScopeIdentifier.Id{coreAndPlugins:settings[:module-configuration]:buildSrc[:module-configuration]:root-project[:module-configuration](export)}

I didn't try, I just have my repositories set up to use milestone/rc versions, and got PRs, so I thought I would give you a heads up.

I so far haven’t gotten config cache working with the new environment var secret with Gradle 8.6 milestone 1. Probably have something misconfigured, will write when I know more definitively