Execute your Gradle build and trigger dependency submission
Find a file
2019-09-22 11:06:17 +02:00
.github/workflows Initial commit 2019-09-20 23:06:59 +02:00
__tests__ Initial commit 2019-09-20 23:06:59 +02:00
src Initial impl 2019-09-21 16:01:53 +02:00
.gitignore better .gitignore 2019-09-22 11:06:17 +02:00
action.yml Initial impl 2019-09-21 16:01:53 +02:00
CODE_OF_CONDUCT.md add code of conduct 2019-09-21 20:57:04 +02:00
jest.config.js Initial commit 2019-09-20 23:06:59 +02:00
LICENSE Initial commit 2019-09-20 23:06:59 +02:00
package-lock.json fix package.json 2019-09-21 16:09:41 +02:00
package.json fix package.json 2019-09-21 16:09:41 +02:00
README.md refine readme 2019-09-21 21:02:16 +02:00
tsconfig.json Initial impl 2019-09-21 16:01:53 +02:00

Execute Gradle commands in Github Actions workflows

This Github Action can be used to run arbitrary Gradle commands on any platform supported by Github Actions.

You might also be interested by the related Gradle Plugin that allows your build to easily get Github Actions environment and tag Gradle Build Scans accordingly.

Usage

The following workflow will run gradle build using the wrapper from the repository on ubuntu, macos and windows:

// .github/workflows/gradle-build-pr.yml
name: Run Gradle on PRs
on: pull-request
jobs:
  gradle:
    strategy:
      matrix:
        os: [ubuntu-latest, macos-latest, windows-latest]
    runs-on: ${{ matrix.os }}
    steps:
    - uses: actions/checkout@v1
    - uses: actions/setup-java@v1
      with:
        java-version: 11
    - uses: eskatos/gradle-command-action@v1
      with:
        arguments: build

Gradle arguments

The arguments input can used to pass arbitrary arguments to the gradle command line.

Here are some valid examples:

arguments: build
arguments: check --scan
arguments: some arbitrary tasks
arguments: build -PgradleProperty=foo
arguments: build -DsystemProperty=bar
....

See gradle --help for more information.

If you need to pass environment variables, simply use the Github Actions workflow syntax:

- uses: eskatos/gradle-command-action@v1
  env:
    CI: true

Run a build from a different directory

- uses: eskatos/gradle-command-action@v1
  with:
    build-root-directory: some/subdirectory

Use a Gradle wrapper from a different directory

 - uses: eskatos/gradle-command-action@v1
   with:
     wrapper-directory: path/to/wrapper-directory

Use a specific gradle executable

 - uses: eskatos/gradle-command-action@v1
   with:
     gradle-executable: path/to/gradle

Setup and use a declared Gradle version

 - uses: eskatos/gradle-command-action@v1
   with:
     gradle-version: 5.6.2

gradle-version can be set to any valid Gradle version.

Moreover, you can use the following aliases:

Alias Selects
current The current stable release
rc The current release candidate if any, otherwise fallback to current
nightly The latest nightly, fails if none.
release-nightly The latest release nightly, fails if none.

This can be handy to automatically test your build with the next Gradle version once a release candidate is out:

// .github/workflows/test-gradle-rc.yml
name: Test latest Gradle RC
on:
  schedule:
    - cron: 0 0 * * * # daily
jobs:
  gradle-rc:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - uses: actions/setup-java@v1
      with:
        java-version: 11
    - uses: eskatos/gradle-command-action@v1
      with:
        gradle-version: rc
        arguments: build --dry-run # just test build configuration

Build scans

If your build publishes a build scan the gradle-command-action action will emit the link to the published build scan as an output named build-scan-url.

You can then use that link in subsequent actions of your workflow.