From b946c060aa4e5d012440d87b9e1eaf8e3e65f1f8 Mon Sep 17 00:00:00 2001 From: Daz DeBoer Date: Sun, 20 Aug 2023 14:05:33 -0600 Subject: [PATCH] Document the `gradle-version` output parameter --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 27382a4..424ed30 100644 --- a/README.md +++ b/README.md @@ -71,6 +71,8 @@ Moreover, you can use the following aliases: This can be handy to automatically verify your build works with the latest release candidate of Gradle: +The actual Gradle version used is available as an action output: `gradle-version`. + ```yaml name: Test latest Gradle RC on: @@ -86,11 +88,14 @@ jobs: distribution: temurin java-version: 11 - uses: gradle/gradle-build-action@v2 + id: setup-gradle with: gradle-version: release-candidate - run: gradle build --dry-run # just test build configuration + - run: echo "The release-candidate version was ${{ steps.setup-gradle.outputs.gradle-version }}" ``` + ## Caching build state between Jobs The `gradle-build-action` will use the GitHub Actions cache to save and restore reusable state that may be speed up a subsequent build invocation. This includes most content that is downloaded from the internet as part of a build, as well as expensive to create content like compiled build scripts, transformed Jar files, etc.