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

Screenshot 2023-07-26 at 16.16.36.png

Missing context: are your Jenkins slaves ephemeral, like GHA runners are?  If not you’ll need to work through caching on GHA for symmetry.

If you are talking about caching the android SDK yes

Not just that.  Are you using gradle-build-action with caching enabled to execute your Gradle build?

and do you have the build cache enabled? (generally via gradle.properties)

This is how we are using the gradle-build-action
    `- name: Setup Gradle`
      `uses: gradle/gradle-build-action@v2.5.1`
      `with:`
        `cache-read-only: false # for debugging`
        `gradle-home-cache-excludes: caches`

Yes we have the remote build cache enabled

why this exclude: `gradle-home-cache-excludes: caches`?  That prevents caching of pretty much everything that Gradle caches.

no.  you are excluding far more than just the build cache.    Build cache is `caches/build-cache-1`.

Not familiar enough with remote cache to know if the local cache should be disabled as well.

Maybe you can enable VFS explicitly with
```org.gradle.vfs.watch=true ```
Gradle does some probing if VFS can be enabled if not enabled explicitly and via network that can be slower. If that doesn't help you can also try to disable it.

&gt; Not familiar enough with remote cache to know if the local cache should be disabled as well.
We are disabling the local cache since the agents are ephemeral.

There’s confusion here.  Yes, the agents are ephemeral - that’s why you have the gradle-build-action to cache between runs.
A clean setup of this:
• disable local build cache (the output from your build scan shows this is already done);
• Remove `gradle-home-cache-excludes: caches` from gradle-build-action to cache everything else (dependencies, etc).  It would cache the local build cache - but that’s disabled.

&gt; Maybe you can enable VFS explicitly with
Tried it also and it doesn’t have any effect on the build time.

Thanks <@U02S31Y7J2K> for your answers.
Mainly removing  `gradle-home-cache-excludes: caches` didn’t have any effect to improving the fingerprinting issue, otherwise we are trying to investigate from our side by combining and playing with different infra configurations, because we noticed that there is some improvements when we changed Memory instead of disk IO access.