No description
Find a file
daz 169bec5d8b
Provision latest Gradle for cache-cleanup
To cleanup Gradle User Home, a Gradle build must be executed.
Newer Gradle versions are able to cleanup the home directories of older versions,
but not vice-versa.

With this change, the latest version of Gradle is automatically provisioned
in order to run Gradle User Home cleanup. This ensures a consistent version of
Gradle is used for cleanup, and fixes #33 where Gradle is not pre-installed on
a custom runner.
2024-06-28 12:39:09 -06:00
.github Rename Develocity secret 2024-06-27 18:49:52 -06:00
dependency-submission Add support for short-lived tokens (#224) 2024-05-15 16:49:55 -06:00
dist [bot] Update dist directory 2024-06-27 20:12:25 +00:00
docs Fix grammar in docs 2024-06-20 07:58:28 -05:00
setup-gradle Adding Develocity input actions (#244) 2024-06-13 12:42:47 -06:00
sources Provision latest Gradle for cache-cleanup 2024-06-28 12:39:09 -06:00
wrapper-validation Documentation updates (#187) 2024-04-18 09:39:15 -06:00
.gitignore Include VS code workspace file 2024-04-12 15:39:30 -06:00
action.yml Move top-level action to 'setup-gradle' 2024-01-25 11:53:44 -07:00
actions.code-workspace Include VS code workspace file 2024-04-12 15:39:30 -06:00
build Add support for short-lived tokens (#224) 2024-05-15 16:49:55 -06:00
CODE_OF_CONDUCT.md add code of conduct 2019-09-21 20:57:04 +02:00
CONTRIBUTING.md Remove instructions for merging Dependabot PRs 2024-06-27 19:32:31 -06:00
LICENSE Update copyright notice 2023-06-30 08:57:49 -06:00
README.md Documentation updates (#187) 2024-04-18 09:39:15 -06:00
RELEASING.md Update releasing guide 2024-04-12 14:01:48 -06:00

GitHub Actions for Gradle builds

This repository contains a set of GitHub Actions that are useful for building Gradle projects on GitHub.

The setup-gradle action

The setup-gradle action can be used to configure Gradle for optimal execution on any platform supported by GitHub Actions.

This replaces the previous gradle/gradle-build-action, which now delegates to this implementation.

The recommended way to execute any Gradle build is with the help of the Gradle Wrapper, and the examples assume that the Gradle Wrapper has been configured for the project. See this example if your project doesn't use the Gradle Wrapper.

Example usage

name: Build

on:
  push:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout sources
      uses: actions/checkout@v4
    - name: Setup Java
      uses: actions/setup-java@v4
      with:
        distribution: 'temurin'
        java-version: 17
    - name: Setup Gradle
      uses: gradle/actions/setup-gradle@v3
    - name: Build with Gradle
      run: ./gradlew build

See the full action documentation for more advanced usage scenarios.

The dependency-submission action

Generates and submits a dependency graph for a Gradle project, allowing GitHub to alert about reported vulnerabilities in your project dependencies.

The following workflow will generate a dependency graph for a Gradle project and submit it immediately to the repository via the Dependency Submission API. For most projects, this default configuration should be all that you need.

Simply add this as a new workflow file to your repository (eg .github/workflows/dependency-submission.yml).

name: Dependency Submission

on:
  push:
    branches: [ 'main' ]

permissions:
  contents: write

jobs:
  dependency-submission:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout sources
      uses: actions/checkout@v4
    - name: Setup Java
      uses: actions/setup-java@v4
      with:
        distribution: 'temurin'
        java-version: 17
    - name: Generate and submit dependency graph
      uses: gradle/actions/dependency-submission@v3

See the full action documentation for more advanced usage scenarios.

The wrapper-validation action

The wrapper-validation action validates the checksums of all Gradle Wrapper JAR files present in the repository and fails if any unknown Gradle Wrapper JAR files are found.

The action should be run in the root of the repository, as it will recursively search for any files named gradle-wrapper.jar.

Example workflow

name: "Validate Gradle Wrapper"

on:
  push:
  pull_request:

jobs:
  validation:
    name: "Validation"
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: gradle/actions/wrapper-validation@v3

See the full action documentation for more advanced usage scenarios.