Repository navigation
Recommend first party Gradle action instead of cache: gradle #588
Description
Activity
- changed the title
[-]Recommend first party Gradle plugin instead of `cache: gradle`[/-][+]Recommend first party Gradle action instead of `cache: gradle`[/+]on Jan 28, 2024 Hello @TWiStErRob
Thank you for creating this feature request. We will investigate it and get back to you as soon as we have some feedback.Is there any update on this request?
The official GitHub docs for Java with Gradle recommend using
gradle/actions/setup-gradleReacted by Róbert PappHello Everyone👋,
Thank you for your feedback and suggestions. We've updated the README as part of the merged PR#972 to highlight the use ofgradle/actions/setup-gradlefor advancedGradlecaching needs and to help users choose the most suitable caching solution for their projects.Since this feature request has now been addressed, I will proceed to close the issue for now. Please feel free to reach out if you have any further questions or concerns. Thank you once again for your input and understanding!
- added a commit that references this issue
on Feb 4, 2026 - added a commit that references this issue
on Apr 15, 2026 - added a commit that references this issue
on May 19, 2026
Description:
Deprecate/remove
cache: gradleoption in favor of a first party Gradle action.If this is not an option, at least mention
gradle/actions/setup-gradlein the documentation ANDaction.ymldescription.Justification:
setup-java tries to do too much. gradle/actions/setup-gradle (ex. gradle-build-action) is a fully featured, advanced GitHub Action for caching Gradle builds outputs. It now includes support for things that'll likely never be part of
setup-java(e.g. configuration cache caching), leaving users confused and using potentially sub-optimal caching strategies. (example: gradle/gradle#13510 (comment))Are you willing to submit a PR?
I'll let maintainers handle deprecations / removals, as that's a complex process.