v3.0.0

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 [email protected] 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 (#946)
• [NEW] - Support for save & restore of configuration-cache data (#966)
• [NEW] - Support for automatic adding PR comment with Job Summary content (#1020)
• [NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com (#1044)
• [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 (#1036). Failure modes include:
  • Fail build step if version of Gradle being executed is not supported for dependency-graph generation (#1034)
  • Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API (#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 (#1017)
  • 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 (#1024)
  • 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 (#995)
• [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 (#996)
• [BREAKING CHANGE] - Remove the gradle-executable input parameter. Use a separate workflow Step to execute a Gradle from a custom location.

v3.0.0-rc.2

Release candidate for gradle/[email protected].
This release candidate will be available under 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.

v3.0.0-rc.1

First release candidate of gradle/[email protected].
This release candidate will the first release available under 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.

v3.0.0-beta.6

Beta release of gradle-build-action@v3.
Can be referenced via gradle/[email protected] or gradle/gradle-build-action@v3-beta.

There are no functional changes in this release.
However, as of this release, gradle/gradle-build-action has been superceded by gradle/actions/setup-gradle.
Any workflow that uses gradle/gradle-build-action@v3* will now 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.

v3.0.0-beta.5

Beta release of gradle-build-action@v3.
Can be referenced via gradle/[email protected] or gradle/gradle-build-action@v3-beta.

• Add dependency-graph: clear option to clear any dependency-graph previously submitted by the job
• Make it easy to publish a Build Scan® to https://scans.gradle.com (#1044)

Full Changelog: v3.0.0-beta.4...v3.0.0-beta.5

v2.12.0

Adds a new option to clear a previously submitted dependency-graph.

steps:
- uses: gradle/gradle-build-action@v2
  with:
    dependency-graph: clear

This may prove useful when migrating to a workflow using the upcoming gradle/actions/dependency-submission action.

Full-changelog: v2.11.1...v2.12.0

v3.0.0-beta.4

Beta release of gradle-build-action@v3.
Can be referenced via gradle/[email protected] or gradle/gradle-build-action@v3-beta.

• Remove the gradle-executable input parameter. Use a separate workflow Step to execute a Gradle from a custom location.
• Update the Gradle Enterprise injection configuration for product rename to Develocity (#995)
• Avoid submitting an empty dependency graph when state is loaded from configuration-cache
• Added dependency-graph-continue-on-failure input, which can be set to false to force the Job to fail when dependency graph submission fails (#1036). Failure modes include:
  • Fail build step if version of Gradle being executed is not supported for dependency-graph generation (#1034)
  • Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API (#997)
• Fix delay in post-action that was introduced when upgrading to Node 20 (#1038)

v3.0.0-beta.3

Beta release of gradle-build-action@v3.
Can be referenced via gradle/[email protected] or gradle/gradle-build-action@v3-beta.

• Allow cache entries to be reused by jobs with the same ID in different workflows (#1017)
  • Workflow name remains part of the cache key, but cache entries generated by the same job id in a different workflow may be restored
• Register pre-installed JDKs in Maven toolchains.xml file (#1024)
  • This allows pre-installed JDKs to be auto-detected by Gradle Toolchain support

v3.0.0-beta.2

Beta release of gradle-build-action@v3.

• Adds support for automatic adding PR comment with Job Summary content (#1020)

v3.0.0-beta.1

First beta release of v3.x

• Support for save & restore of configuration-cache data #966
• Switch to run with NodeJs 20.x #946
• Deprecation of the arguments parameter #996