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
Update: tool-cache does not cache files across job executions in GitHub runners (see actions/toolkit#58 (comment)), so currently tool-cache is not useful for caching gradle-generated-jars
The text was updated successfully, but these errors were encountered:
There's another aspect to this. Gradle can generate three different JARs in that directory, the gradle-api jar, the gradle-kotlin-dsl-extensions jar and the gradle-test-kit jar. Those are generated on-demand so which jars get generated depends on what the run build does.
As tool-cache is not reused across GitHub runners, it makes little sense to cache it into the tool-cache, so I close the issue as there's nothing to do :-(
It looks like the way to go is to solve gradle/gradle#13982 somehow (e.g. use classpath-only jar instead of a full-blown jar)
Have you tried caching generated-gradle-jars into
tool-cache
as well?In other words:
.gradle/caches/6.6/generate-gradle-jars/...
generated-gradle-jars
is cached intotool-cache
(e.g. copy it togradle
location)generated-gradle-jars
accordinglySee gradle/gradle#13982
Update:
tool-cache
does not cache files across job executions in GitHub runners (see actions/toolkit#58 (comment)), so currently tool-cache is not useful for cachinggradle-generated-jars
The text was updated successfully, but these errors were encountered: