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
The distributionPath property in gradle/wrapper/gradle-wrapper.properties is not used when caching distributions. It appears that caching is only supported for the default wrapper/dists location.
The text was updated successfully, but these errors were encountered:
Thanks for the report: you're assessment is correct. Currently the gradle-build-action can only save/restore wrapper downloads that are located in the default location. Are you setting only distributionPath or are you also specifying distributionBase in gradle-wrapper.properties?
You can configure the action to save/restore more directories inside the Gradle User Home directory, but there's no way to tell the action to save/restore directories outside of the Gradle User Home.
As a workaround:
If your wrapper dists are located in a different location in Gradle User Home, you could configure gradle-home-cache-includes with the extra location.
If your wrapper dists are located outside of Gradle User Home, then you could setup caching of this directory with actions/cache
Is there specific cache logic for wrapper/dists that wouldn't be applied using a generic gradle-home-cache-includes?
Yes, the Gradle wrapper distributions are saved and restored independently of the rest of the Gradle User Home, with the aim to increase sharing between different projects/builds using the same Gradle version.
bigdaz
changed the title
distributionPath property not honored when caching distributions
Honor custom distributionPath for caching downloaded wrapper distributions
Feb 18, 2023
bigdaz
transferred this issue from gradle/gradle-build-action
Feb 9, 2024
The
distributionPath
property ingradle/wrapper/gradle-wrapper.properties
is not used when caching distributions. It appears that caching is only supported for the defaultwrapper/dists
location.The text was updated successfully, but these errors were encountered: