Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update gradle/gradle-build-action action to v2.8.0 {patch} #458

Merged
merged 1 commit into from
Aug 28, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 28, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
gradle/gradle-build-action action minor v2.7.1 -> v2.8.0

Release Notes

gradle/gradle-build-action (gradle/gradle-build-action)

v2.8.0

Compare Source

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:

Changes

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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, check this box

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

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@nagyesta nagyesta added the dependency Dependency update label Aug 28, 2023
@codecov
Copy link

codecov bot commented Aug 28, 2023

Codecov Report

Merging #458 (3717947) into main (f68878f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #458   +/-   ##
=========================================
  Coverage     77.02%   77.02%           
  Complexity      173      173           
=========================================
  Files            22       22           
  Lines           470      470           
  Branches         15       15           
=========================================
  Hits            362      362           
  Misses           98       98           
  Partials         10       10           
Flag Coverage Δ
core ?
cucumber 92.79% <ø> (ø)
flighteval ∅ <ø> (∅)
junit4 83.05% <ø> (ø)
jupiter 87.06% <ø> (ø)
testkit 36.97% <ø> (ø)
testng 100.00% <ø> (ø)

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

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

@nagyesta nagyesta merged commit 6df8f3b into main Aug 28, 2023
@nagyesta nagyesta deleted the renovate/gradle-gradle-build-action-2.x branch August 28, 2023 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency Dependency update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant