Update gradle/gradle-build-action action to v2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
gradle/gradle-build-action	action	major	v1.5.0 -> v2.1.0

---

Release Notes

gradle/gradle-build-action

v2.1.0

Compare Source

Overview

This release brings a major improvement in usability, allowing the action to be used to "setup Gradle" without requiring all Gradle invocations to be managed by the action.

jobs:
  build-my-app:
    steps:
    - uses: actions/checkout@v2
    - name: Setup Gradle
      uses: gradle/gradle-build-action@v2
    - name: Execute Gradle build
      run: ./gradlew build

Any Gradle invocation after the first gradle-build-action step will benefit from caching and build-scan capture just as if it was invoked through a subsequent gradle-build-action. This is achieved via init scripts added when initializing/restoring the Gradle User Home.

This change makes it easier to adopt the gradle-build-action into an existing GitHub Actions workflow and enables usages such as:

• Redirect all Gradle log output to a file #​72
• Run a script to configure the environment prior to Gradle invocation #​15
• Capture Gradle output for use in a subsequent step #​112

Usability improvements

• Can use regular run step to invoke Gradle and still benefit from Gradle User Home caching as well as build-scan integration.

Caching improvements

• Wrapper distributions and generated API jars are now cached individually, allowing for better reuse and more efficient storage: #​78
• Java distributions downloaded by Gradle are cached: #​33

Changes in detail

• Avoid using command-line modification to enhance build execution by @​bigdaz in https://github.com/gradle/gradle-build-action/pull/123
• Refactor: use a single .json file to describe all cached artifact bundles by @​bigdaz in https://github.com/gradle/gradle-build-action/pull/121
• Cache wrapper zips and generated jars individually by @​bigdaz in https://github.com/gradle/gradle-build-action/pull/127
• Restore/save configuration-cache data in first action step by @​bigdaz in https://github.com/gradle/gradle-build-action/pull/128
• Allow action to be used without Gradle execution by @​bigdaz in https://github.com/gradle/gradle-build-action/pull/130
• Cache downloaded Java Toolchains by @​bigdaz in https://github.com/gradle/gradle-build-action/pull/131

Full Changelog: gradle/gradle-build-action@v2.0.0...v2.1.0

v2.0.1

Compare Source

What's Changed

This patch release fixes a couple of cases where a failure to store caches would cause the entire Job to fail. The goal of the gradle-build-action is to warn-and-continue on all recoverable cache failures.

Issues fixed

• Cache upload failure because file read failed should not cause step to fail #​120
• SyntaxError: Unexpected end of JSON input should not cause step to fail #​119

Full Changelog: gradle/gradle-build-action@v2.0.0...v2.0.1

v2.0.0

Compare Source

This is the initial release of gradle-build-action@v2, which brings significant performance and usability improvements over v1. A few key improvements are outlined here, but see the project README for more details.

Thanks for trying it out!

Usability improvements:

The gradle-build-action has been redesigned from the ground up to work well with minimal configuration, avoiding the need for most users to tweak multiple configuration options to benefit.

Highlights:

• Simplified and improved configuration options, with better support for more Gradle builds "out of the box".
• More robust capture of Build Scan™ links, which are now added directly as Notice annotations to your workflow run.
• Support for multi-line arguments in workflow definitions.

Performance improvements:

A key benefit of gradle-build-action over other solutions is the sophisticated support for saving and restoring relevant Gradle state between build invocations. This caching support speeds up build invocations and is designed to work in most scenarios without further tweaking.

Highlights:

• Support for caching of more state between Gradle invocations, including compiled build scripts and generated Gradle API jars as well as downloaded dependencies and Gradle distributions.
• Common files such as downloaded dependencies and wrapper distributions are cached in a more efficient manner, with the goal to cut cache-entry size and reduce eviction pressure.
• Detailed reporting of cache usage and cache configuration options allow you to optimize the use of the GitHub actions cache.

v1.5.1

Compare Source

Fixes issue where invalid cache keys could be generated if the Gradle arguments list was overly long.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.