Handling Maven GitLab dependencies made easy. Define multiple tokens and selectively apply them to repositories, remove the need for repeating Credential handling blocks for different environments.
Eclipse Public License 2.0
13
stars
1
forks
source link
Update eskatos/gradle-command-action action to v2 #30
eskatos/gradle-command-action
### [`v2.1.2`](https://togithub.com/eskatos/gradle-command-action/releases/v2.1.2)
[Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v2.1.1...v2.1.2)
This patch release fixes a minor bug and updates some NPM dependencies, including one dependency with a reported security advisory.
##### What's Changed
- Fixed [#147](https://togithub.com/eskatos/gradle-command-action/issues/147): existing `gradle.properties` is no longer overwritten by action initialization
- Updated all NPM dependencies to the latest version
- This included updating `node-fetch` to a version that isn't impacted by https://github.com/advisories/GHSA-r683-j2x4-v87g. Note that this CVE has been determined not to impact the action.
**Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.1...v2.1.2
### [`v2.1.1`](https://togithub.com/eskatos/gradle-command-action/releases/v2.1.1)
[Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v2.1.0...v2.1.1)
This release improves logging and fixes a number of minor issues.
- Fix misleading error message when `gradlew` script is not executable [#76](https://togithub.com/eskatos/gradle-command-action/issues/76)
- Differentiate between build scan links generated for different steps in the same Job [#124](https://togithub.com/eskatos/gradle-command-action/issues/124)
- Avoid overwriting existing Gradle User Home [#138](https://togithub.com/eskatos/gradle-command-action/issues/138)
- Capture build scan links even when cache is disabled [#139](https://togithub.com/eskatos/gradle-command-action/issues/139)
In addition, 2 experimental configuration parameters have been added:
- `gradle-home-cache-strict-match`: Only reuse cache entries generated by previous invocations for the same job
- `cache-write-only`: Do not restore cache entries but save on Job completion
**Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.0...v2.1.1
### [`v2.1.0`](https://togithub.com/eskatos/gradle-command-action/releases/v2.1.0)
[Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v2.0.1...v2.1.0)
##### 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.
```yaml
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](https://togithub.com/eskatos/gradle-command-action/issues/72)
- Run a script to configure the environment prior to Gradle invocation [#15](https://togithub.com/eskatos/gradle-command-action/issues/15)
- Capture Gradle output for use in a subsequent step [#112](https://togithub.com/eskatos/gradle-command-action/issues/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](https://togithub.com/eskatos/gradle-command-action/issues/78)
- Java distributions downloaded by Gradle are cached: [#33](https://togithub.com/eskatos/gradle-command-action/issues/33)
##### Changes in detail
- Avoid using command-line modification to enhance build execution by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/123](https://togithub.com/gradle/gradle-build-action/pull/123)
- Refactor: use a single .json file to describe all cached artifact bundles by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/121](https://togithub.com/gradle/gradle-build-action/pull/121)
- Cache wrapper zips and generated jars individually by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/127](https://togithub.com/gradle/gradle-build-action/pull/127)
- Restore/save configuration-cache data in first action step by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/128](https://togithub.com/gradle/gradle-build-action/pull/128)
- Allow action to be used without Gradle execution by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/130](https://togithub.com/gradle/gradle-build-action/pull/130)
- Cache downloaded Java Toolchains by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/131](https://togithub.com/gradle/gradle-build-action/pull/131)
**Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.0.0...v2.1.0
### [`v2.0.1`](https://togithub.com/eskatos/gradle-command-action/releases/v2.0.1)
[Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v2.0.0...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](https://togithub.com/eskatos/gradle-command-action/issues/120)
- SyntaxError: Unexpected end of JSON input should not cause step to fail [#119](https://togithub.com/eskatos/gradle-command-action/issues/119)
**Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.0.0...v2.0.1
### [`v2.0.0`](https://togithub.com/eskatos/gradle-command-action/releases/v2.0.0)
[Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v1.5.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](README.md) 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.
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 contains the following updates:
v1.5.1->v2.1.2Release Notes
eskatos/gradle-command-action
### [`v2.1.2`](https://togithub.com/eskatos/gradle-command-action/releases/v2.1.2) [Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v2.1.1...v2.1.2) This patch release fixes a minor bug and updates some NPM dependencies, including one dependency with a reported security advisory. ##### What's Changed - Fixed [#147](https://togithub.com/eskatos/gradle-command-action/issues/147): existing `gradle.properties` is no longer overwritten by action initialization - Updated all NPM dependencies to the latest version - This included updating `node-fetch` to a version that isn't impacted by https://github.com/advisories/GHSA-r683-j2x4-v87g. Note that this CVE has been determined not to impact the action. **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.1...v2.1.2 ### [`v2.1.1`](https://togithub.com/eskatos/gradle-command-action/releases/v2.1.1) [Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v2.1.0...v2.1.1) This release improves logging and fixes a number of minor issues. - Fix misleading error message when `gradlew` script is not executable [#76](https://togithub.com/eskatos/gradle-command-action/issues/76) - Differentiate between build scan links generated for different steps in the same Job [#124](https://togithub.com/eskatos/gradle-command-action/issues/124) - Avoid overwriting existing Gradle User Home [#138](https://togithub.com/eskatos/gradle-command-action/issues/138) - Capture build scan links even when cache is disabled [#139](https://togithub.com/eskatos/gradle-command-action/issues/139) In addition, 2 experimental configuration parameters have been added: - `gradle-home-cache-strict-match`: Only reuse cache entries generated by previous invocations for the same job - `cache-write-only`: Do not restore cache entries but save on Job completion **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.0...v2.1.1 ### [`v2.1.0`](https://togithub.com/eskatos/gradle-command-action/releases/v2.1.0) [Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v2.0.1...v2.1.0) ##### 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. ```yaml 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](https://togithub.com/eskatos/gradle-command-action/issues/72) - Run a script to configure the environment prior to Gradle invocation [#15](https://togithub.com/eskatos/gradle-command-action/issues/15) - Capture Gradle output for use in a subsequent step [#112](https://togithub.com/eskatos/gradle-command-action/issues/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](https://togithub.com/eskatos/gradle-command-action/issues/78) - Java distributions downloaded by Gradle are cached: [#33](https://togithub.com/eskatos/gradle-command-action/issues/33) ##### Changes in detail - Avoid using command-line modification to enhance build execution by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/123](https://togithub.com/gradle/gradle-build-action/pull/123) - Refactor: use a single .json file to describe all cached artifact bundles by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/121](https://togithub.com/gradle/gradle-build-action/pull/121) - Cache wrapper zips and generated jars individually by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/127](https://togithub.com/gradle/gradle-build-action/pull/127) - Restore/save configuration-cache data in first action step by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/128](https://togithub.com/gradle/gradle-build-action/pull/128) - Allow action to be used without Gradle execution by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/130](https://togithub.com/gradle/gradle-build-action/pull/130) - Cache downloaded Java Toolchains by [@bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/131](https://togithub.com/gradle/gradle-build-action/pull/131) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.0.0...v2.1.0 ### [`v2.0.1`](https://togithub.com/eskatos/gradle-command-action/releases/v2.0.1) [Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v2.0.0...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](https://togithub.com/eskatos/gradle-command-action/issues/120) - SyntaxError: Unexpected end of JSON input should not cause step to fail [#119](https://togithub.com/eskatos/gradle-command-action/issues/119) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.0.0...v2.0.1 ### [`v2.0.0`](https://togithub.com/eskatos/gradle-command-action/releases/v2.0.0) [Compare Source](https://togithub.com/eskatos/gradle-command-action/compare/v1.5.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](README.md) 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.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.
This PR has been generated by WhiteSource Renovate. View repository job log here.