Update gradle/gradle-build-action action to v3 - #166

v3.1.0

Compare Source

[!IMPORTANT]
As of v3 this action has been superceded by gradle/actions/setup-gradle.
Any workflow that uses gradle/gradle-build-action@v3 will transparently delegate to gradle/actions/setup-gradle@v3.

Users are encouraged to update their workflows, replacing:

uses: gradle/gradle-build-action@v3

with

uses: gradle/actions/setup-gradle@v3

See the setup-gradle documentation for up-to-date documentation for gradle/actions/setup-gradle.

For release details, see https://github.com/gradle/actions/releases/tag/v3.1.0

v3.0.0

Compare Source

This is the first release of gradle/gradle-build-action available with the v3 version tag.

[!IMPORTANT]
As of v3 this action has been superceded by gradle/actions/setup-gradle.
Any workflow that uses gradle/gradle-build-action@v3 will transparently delegate to gradle/actions/setup-gradle@v3.

Users are encouraged to update their workflows, replacing:

uses: gradle/gradle-build-action@v3

with

uses: gradle/actions/setup-gradle@v3

See the setup-gradle documentation for up-to-date documentation for gradle/actions/setup-gradle.

Changes from gradle-build-action@v2

This release brings some useful and much requested features, including:

• save and restore the Gradle configuration-cache data
• add the Job summary content as a PR comment
• easily publish Build Scans® to the free Gradle Build Scan service
• compatibility with Node 20

The only major breaking change from gradle-build-action@v2.12.0 is the update to require a Node 20 runtime environment.
Aside from that change, this release should generally serve as a drop-in replacement for gradle-build-action@v2.

Changelog

• [NEW] - Run with NodeJs 20.x https://github.com/gradle/gradle-build-action/issues/9466)
• [NEW] - Support for save & restore of configuration-cache data https://github.com/gradle/gradle-build-action/issues/9666)
• [NEW] - Support for automatic adding PR comment with Job Summary content https://github.com/gradle/gradle-build-action/issues/10200)
• [NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com https://github.com/gradle/gradle-build-action/issues/10444)
• [NEW] - Added dependency-graph-continue-on-failure input, which can be set to false to force the Job to fail when dependency graph submission fails (https://github.com/gradle/gradle-build-action/issues/1036). Failure modes include:
  • Fail build step if version of Gradle being executed is not supported for dependency-graph generation (https://github.com/gradle/gradle-build-action/issues/1034)
  • Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API (https://github.com/gradle/gradle-build-action/issues/997)
• [NEW] - Add dependency-graph: clear option to clear any dependency-graph previously submitted by the job
• [FIX] Allow cache entries to be reused by jobs with the same ID in different workflows https://github.com/gradle/gradle-build-action/issues/10177)
  • Workflow name remains part of the cache key, but cache entries generated by the same job id in a different workflow may be restored
• [FIX] Register pre-installed JDKs in Maven toolchains.xml file https://github.com/gradle/gradle-build-action/issues/10244)
  • This allows pre-installed JDKs to be auto-detected by Gradle Toolchain support on Windows
• [FIX] - Update the Gradle Enterprise injection configuration for product rename to Develocity https://github.com/gradle/gradle-build-action/issues/9955)
• [FIX] - Avoid submitting an empty dependency graph when state is loaded from configuration-cache
• [FIX] - Update to GitHub Dependency Graph Gradle Plugin v1.2.0
• [DEPRECATION] - Deprecation of the arguments parameter https://github.com/gradle/gradle-build-action/issues/9966)
• [BREAKING CHANGE] - Remove the gradle-executable input parameter. Use a separate workflow Step to execute a Gradle from a custom location.