From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

image.png

Nothing more than setting the env variable, in the specified format, is required.  What do you believe is missing?

What cache directories should be uploaded and downloaded?

Does gradle recommend uploading/downloading or a shared network volume? etc

That has nothing to do with the encryption key.  Iirc the docs indicate that cc is not relocatable, though it does work across identical machines (ie CI runners).  Checkout the gradle-build-action GitHub action sources for internal details.

the encryption key allows for the second case you mentioned (identical paths on CI runners), and my post is suggesting documenting a workflow for doing that.

> Checkout the gradle-build-action GitHub action sources for internal details.
Sure, but that this is not a good substitute for documentation.

Cc is documented as not relocatable - if you want to share it use a Gradle-provided mechanism (gradle-build-action) or figure out the internals.

It's maybe worth pointing out that the docs for the new encryption key env _also_ don't link/suggest any gradle-provided mechanisms like the github actions. I'm just asking for more docs and guidance on this page, first-party or otherwise.

I also think it's a little unhelpful/circular just referencing a doc that I'm suggesting could be improved, so mind if I ask if we just park it here and leave it to gradle folks to take up if they're interested?

<https://github.com/gradle/gradle-build-action#saving-configuration-cache-data|https://github.com/gradle/gradle-build-action#saving-configuration-cache-data>

&gt; we just park it here and leave it to gradle folks to take up if they're interested?
&gt; 
It is very unlikely it is picked up when parking it here, as this is mainly a community Slack.
I'd suggest you create a documentation issue on GitHub, then the chances for a pick-up are much higher.

It's always possible to tag <@UAF4ZBBBN> (maintainer of said actions) as FYI, but otherwise, if you had created an issue, I'd like to follow it, <@UNLAD20BW>!

The `setup-gradle` action will only restore the configuration cache if _everything_ in `&lt;gradle-user-home&gt;/caches` is restored. The configuration-cache data links directly to files in this directory, and I don't have a good insight into exactly which ones. It's certainly more than downloaded dependencies, and I think it includes artifact transforms and possibly compiled build scripts.
The CC entry also points relies on the output of any included builds that impact the build-script classpath: see <https://github.com/gradle/actions/issues/21>

So there's still no supported mechanism to reused CC entries between machines. The `setup-gradle` action hacks in _some_ support, much like it hacks in support for cleaning the Gradle User Home directory.
And by "hack", <https://github.com/gradle/actions/blob/main/sources/src/caching/cache-cleaner.ts|I really mean it> :slightly_smiling_face: