You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, the issue with launching Gradle several times is to figure out "how to deal with the shared dependencies cache".
So far I have execution-only-caches: true action property which skips gradle dependencies, maven local repository and similar caches for a particular execution.
Back to your case, I guess it would work if you replace eskatos/gradle-command-action with burrunan/gradle-cache-action 😉 and add execution-only-caches: true (into with:) to the second and the third executions.
Then the first one would fetch dependencies caches, execution-only-caches: true would still use remote build cache, and finally post step of the very first execution would update dependencies cache if needed.
The drawback there would be that dependencies cache would not account for build.gradle.* changes within sample-kotlin and sample-groovy (which is #15)
Here's the link of a workflow that I'd like to update to be more efficient and faster thanks to caching: https://github.com/jmfayard/refreshVersions/blob/c8f1e0c5b9d6e7303fbc97228b8980cd73f53cf0/.github/workflows/check-build.yml
The text was updated successfully, but these errors were encountered: