Daz DeBoer
Daz DeBoer
Fixes #19750 ### Context Previously, setting any value for `org.gradle.jvmargs` caused all default settings to be lost. This often resulted in important defaults like `-XXMaxMetaspaceSize` being omitted when a user...
The Gradle User Home directory is not cleaned up in an efficient manner by Gradle, and this action doesn't do anything special to cleanup unused files in the Gradle User...
There is now an API that permits users to delete specific cache entries. It might be possible to leverage this to overwrite existing cache entries, allowing corrupted cache entries to...
The current Job Summary, while working OK, doesn't render well in some cases with long values. 1. The 'requested tasks' column includes all task options, which can make that column...
Currently, we recommend that users configure a separate workflow running the [wrapper-validation-action](https://github.com/marketplace/actions/gradle-wrapper-validation) to verify that the Gradle wrapper jar is not corrupted. Doing this automatically for any workflow using `gradle-build-action`...
Currently these parameters won't work quite as expected if specified as paths with wildcards.
The gradle-build-action does not attempt to determine which source files control the contents of the different cached "bundles" in Gradle User Home. Instead, a cache key is calculated based on...
It's not unusual for workflows to contain a step following `gradle-build-action` to upload build reports as artifacts, like: ``` - name: Store reports uses: actions/upload-artifact@v2 with: name: linux-reports path: build/reports/...
When the action detects an existing Gradle User Home, it will not attempt to save/restore the Gradle User Home to the GitHub Actions cache. This manifests in a strange way...
Workflows using this action receive deprecation warnings. Please provide a new action release that runs with Node 20. https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/