Movatterモバイル変換

[0]ホーム
URL:

Skip to main content
GitHub Docs

Building and testing Java with Gradle

Learn how to create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Gradle.

Introduction

This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Gradle build system. The workflow you create will allow you to see when commits to a pull request cause build or test failures against your default branch; this approach can help ensure that your code is always healthy. You can extend your CI workflow to cache files and upload artifacts from a workflow run.

GitHub-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Gradle. For a list of software and the pre-installed versions for JDK and Gradle, seeGitHub-hosted runners.

Prerequisites

You should be familiar with YAML and the syntax for GitHub Actions. For more information, see:

We recommend that you have a basic understanding of Java and the Gradle framework. For more information, see theGradle User Manual.

Using a Gradle workflow template

To get started quickly, add a workflow template to the.github/workflows directory of your repository.

GitHub provides a workflow template for Gradle that should work for most Java with Gradle projects. The subsequent sections of this guide give examples of how you can customize this workflow template.

  1. On GitHub, navigate to the main page of the repository.

  2. Under your repository name, click Actions.

    Screenshot of the tabs for the "github/docs" repository. The "Actions" tab is highlighted with an orange outline.

  3. If you already have a workflow in your repository, clickNew workflow.

  4. The "Choose a workflow" page shows a selection of recommended workflow templates. Search for "Java with Gradle".

  5. On the "Java with Gradle" workflow, clickConfigure.This workflow performs the following steps:

  6. Checks out a copy of project's repository.

  7. Sets up the Java JDK.

  8. Sets up the Gradle environment. Thegradle/actions/setup-gradle action takes care of caching state between workflow runs, and provides a detailed summary of all Gradle executions.

  9. The "Build with Gradle" step executes thebuild task using theGradle Wrapper.

  10. Edit the workflow as required. For example, change the Java version.

    Note

    • This workflow template contains an action that is not certified by GitHub. Actions provided by third parties are governed by separate terms of service, privacy policy, and support documentation.
    • If you use actions from third parties you should use a version specified by a commit SHA. If the action is revised and you want to use the newer version, you will need to update the SHA. You can specify a version by referencing a tag or a branch, however the action may change without warning. For more information, seeSecure use reference.

  11. ClickCommit changes.

    Thegradle.yml workflow file is added to the.github/workflows directory of your repository.

Specifying the Java version and architecture

The workflow template sets up thePATH to contain OpenJDK 8 for the x64 platform. If you want to use a different version of Java, or target a different architecture (x64 orx86), you can use thesetup-java action to choose a different Java runtime environment.

For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use thesetup-java action and configure thejava-version,distribution andarchitecture parameters to'11','temurin' andx64.

YAML
steps:-uses:actions/checkout@v5-name:SetupJDK11forx64uses:actions/setup-java@v4with:java-version:'11'distribution:'temurin'architecture:x64

For more information, see thesetup-java action.

Building and testing your code

You can use the same commands that you use locally to build and test your code.

The workflow template will run thebuild task by default. In the default Gradle configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.

If you use different commands to build your project, or you want to use a different task, you can specify those. For example, you may want to run thepackage task that's configured in yourci.gradle file.

YAML
steps:-uses:actions/checkout@v5-uses:actions/setup-java@v4with:java-version:'17'distribution:'temurin'-name:SetupGradleuses:gradle/actions/setup-gradle@017a9effdb900e5b5b2fddfb590a105619dca3c3# v4.4.2-name:BuildwithGradlerun:./gradlew-bci.gradlepackage

Caching dependencies

Your build dependencies can be cached to speed up your workflow runs. After a successful run,gradle/actions/setup-gradle caches important parts of the Gradle user home directory. In future jobs, the cache will be restored so that build scripts won't need to be recompiled and dependencies won't need to be downloaded from remote package repositories.

Caching is enabled by default when using thegradle/actions/setup-gradle action. For more information, seegradle/actions/setup-gradle.

Packaging workflow data as artifacts

After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, seeStore and share data with workflow artifacts.

Gradle will usually create output files like JARs, EARs, or WARs in thebuild/libs directory. You can upload the contents of that directory using theupload-artifact action.

YAML
steps:-uses:actions/checkout@v5-uses:actions/setup-java@v4with:java-version:'17'distribution:'temurin'-name:SetupGradleuses:gradle/actions/setup-gradle@017a9effdb900e5b5b2fddfb590a105619dca3c3# v4.4.2-name:BuildwithGradlerun:./gradlewbuild-name:Uploadbuildartifactsuses:actions/upload-artifact@v4with:name:Packagepath:build/libs
[8]ページ先頭
©2009-2025 Movatter.jp