This message was deleted.

It takes over 1m 20s in Jenkins machines Gradle configuration times (use new physical node for every execution), but in my local machines, it takes about 4s. *There are no significant differences in computing powers. I think there is some caching mechanism in Gradle configuration step. And perhaps I can boost Jenkins Gradle configuration step with this. But I can’t figure out where this cache is and how to leverage it. I’ve already found Configuration Cache(experimental), but I’m not using it, and still, my local configuration step is faster then remote machines.

have you read https://docs.gradle.org/current/userguide/dependency_resolution.html#sub:ephemeral-ci-cache

I think that’s what I was looking for! Local build was faster despite project clean due to dependency cache in my machine’s gradle home. (after remove that cache folder in gradle home, configuration time became slower like Jenkins Machine) I’ll consider sharing dependency cache, thank you 😸