Bump eskatos/gradle-command-action from 1 to 2.0.1

[dependabot]

Bumps eskatos/gradle-command-action from 1 to 2.0.1.

Release notes

Sourced from eskatos/gradle-command-action's releases.

v2.0.1

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

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.

v2.0-rc.2

Adds a useful report outlining cache entries restored/saved, and fixes a few issues found in v2.0-rc.1.

• All dependency files are not included in dependencies cache bundle, instead of just .jar files (#100)
• gradle-home-cache-includes and gradle-home-cache-excludes are now multi-line inputs (#106)
• Only restore configuration-cache state when all of Gradle User Home is restored (#107)
• Report on cache entry keys and sizes in post-action

v2.0-rc.1

This initial rc.1 is the same as 2.0-beta.7, except that a few parameters have been renamed, and a little documentation added.

v2.0-beta.7

• Adds some (experimental) options for fine-tuning the gradle-build-action cache:
  • Specify cache-paths to override the default directories cached from Gradle User Home
  • Specify cache-exclude-paths to exclude files from the Gradle User Home cache
• Files under caches//kotlin-dsl are now cached as a bundle
• Build scan link is included in failure notice when Gradle build fails

... (truncated)

Commits

• 996094e Avoid failing job on any failure in post-action
• 4137be6 Minor improvement to logging in post-action
• 4e89983 Avoid failing build on distributions cache errors
• 3812292 Add CodeQL Analysis (#114)
• c12283e Add a section explaining advantages
• f2dc0d8 Add section on optimizing cache effectiveness
• 717db31 Fix logging of cache key for Gradle User Home
• 2a57ddf Merge pull request #111 from gradle/dd/cache-report
• 230fd6b Build outputs
• 472ac8a Report sizes of cache entries
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #22.