-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Action should use existing Gradle wrapper distributions for cache-cleanup where possible #515
Comments
Thanks for reporting. As a workaround, is it possible to pre-install Gradle >= 8.11 on the runners? If cache-cleanup finds Gradle on the PATH, then no download will be necessary. I agree that re-using existing wrapper distributions would be the optimal solution, but it's not clear when we'll have time to implement this. |
Thanks for providing the workaround. We'll consider that. |
@stefan-rademacher-tk You may have seen that this issue has been resolved. This is done by re-using known an existing wrapper executable for cache-cleanup, assuming that it meets the minimum version requirements (>= 8.11 and at least as new as the newest version that executed a build during the Job). While this has not yet been released, it would be great if you could try out a pre-release version to ensure that it solves your problem:
To verify that it's working, check for a message like this in the action logs. ![]() Thanks! |
Hi. I could successfully avoid the download:
Thank you for fixing this so quickly! |
Hi.
We are using the setup-gradle action with the default configuration 'gradle-version: wrapper'.
In the section ‘Post Setup Gradle’, the action tries to download Gradle 8.11 from services.gradle.org, even though we have a Gradle Wrapper configuration with Gradle 8.10.2 (from an on-premise webserver) configured:
This doesn't work in our corporate network, since the proxy slows down the download drastically.
Would be nice, if ...
The first option seems more appealing to me.
This issue is related to #436.
Thank you, Stefan
The text was updated successfully, but these errors were encountered: