Bump gradle/gradle-build-action from 2.7.0 to 2.9.0

[dependabot[bot]]

Bumps gradle/gradle-build-action from 2.7.0 to 2.9.0.

Release notes

Sourced from gradle/gradle-build-action's releases.

v2.9.0

The GitHub dependency-review-action helps you understand dependency changes (and the security impact of these changes) for a pull request. This release updates the GItHub Dependency Graph support to be compatible with the dependency-review-action.

See the documentation for detailed examples.

Changelog

• [FIX] Use correct SHA for pull-request events #882
• [FIX] Avoid generating dependency graph during cache cleanup #905
• [NEW] Improve warning on failure to submit dependency graph
• [NEW] Compatibility with GitHub dependency-review-action #879

Full-changelog: https://github.com/gradle/gradle-build-action/compare/v2.8.1...v2.9.0

v2.8.1

Fixes an issue that prevented Dependency Graph submission when running on GitHub Enterprise Server.

Fixes

• Incorrect endpoint used to submit Dependency Graph on GitHub Enterprise #885

Changelog

https://github.com/gradle/gradle-build-action/compare/v2.8.0...v2.8.1

v2.8.0

The v2.8.0 release of the gradle-build-action introduces an easy mechanism to connect to Gradle Enterprise, as well improved support for self-hosted GitHub Actions runners.

Automatic injection of Gradle Enterprise connectivity

It is now possible to connect a Gradle build to Gradle Enterprise without changing any of the Gradle project sources. This is achieved through Gradle Enterprise injection, where an init-script will apply the Gradle Enterprise plugin and associated configuration.

This feature can be useful to easily trial Gradle Enterprise on a project, or to centralize Gradle Enterprise configuration for all GitHub Actions workflows in an organization.

See Gradle Enterprise injection in the README for more info.

Restore Gradle User Home when directory already exists

Previously, the Gradle User Home would not be restored if the directory already exists. This wasn't normally an issue with GitHub-hosted runners, but limited the usefulness of the action for persistent, self-hosted runners.

This behaviour has been improved in this release:

• The Job Summary now includes a useful error message when Gradle User Home was not restored because the directory already exists.
• The action can now be configured to restore the Gradle User Home when the directory already exists, overwriting existing content with content from the GitHub Actions cache. See https://github.com/gradle/gradle-build-action#overwriting-an-existing-gradle-user-home for more details.

Changes

Issues fixed: https://github.com/gradle/gradle-build-action/issues?q=milestone%3A2.8.0+is%3Aclosed Full changelog: https://github.com/gradle/gradle-build-action/compare/v2.7.1...v2.8.0

v2.7.1

This release contains no code changes, only dependency updates and documentation improvements.

Changelog

https://github.com/gradle/gradle-build-action/compare/v2.7.0...v2.7.1

Commits

• 842c587 Merge pull request #911 - Improve dependency review support
• 4241e05 Document configuration for dependency-review-action
• bfa3c05 Build outputs
• c3bdce8 Warn on dependency-graph-submit failure
• f92e7c3 Improve compat with dependency-review-action
• d1b726d Do not generate dependency graph in cache-cleanup
• 6fcc109 Dependency updates (#904)
• fde5b4f fix README.md internal references
• 324fbdc Update to dep-graph plugin 0.4.1
• 5658338 Build outputs
• 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

[codecov[bot]]

Codecov Report

Merging #106 (1d78832) into dev (548cbf9) will not change coverage. The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev     #106   +/-   ##
=========================================
  Coverage     92.57%   92.57%           
  Complexity       77       77           
=========================================
  Files             7        7           
  Lines           283      283           
  Branches         20       20           
=========================================
  Hits            262      262           
  Misses           19       19           
  Partials          2        2           

Flag	Coverage Δ
integrationTests	82.68% <ø> (ø)
unitTests	39.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

[dependabot[bot]]

Superseded by #115.