Movatterモバイル変換

[0]ホーム
URL:

Skip to main content
GitHub Docs

Building and testing Java with Maven

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

Introduction

This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Maven software project management tool. 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 Maven. For a list of software and the pre-installed versions for JDK and Maven, 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 Maven framework. For more information, see theMaven Getting Started Guide in the Maven documentation.

Using a Maven workflow template

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

GitHub provides a workflow template for Maven that should work for most Java with Maven 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 Maven".

  5. On the "Java with Maven" workflow, clickConfigure.

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

  7. ClickCommit changes.

    Themaven.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 thepackage target by default. In the default Maven 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 target, you can specify those. For example, you may want to run theverify target that's configured in apom-ci.xml file.

YAML
steps:-uses:actions/checkout@v5-uses:actions/setup-java@v4with:java-version:'17'distribution:'temurin'-name:RuntheMavenverifyphaserun:mvn--batch-mode--update-snapshotsverify

Caching dependencies

You can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored in a cache. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. You can cache dependencies simply using thesetup-java action or can usecache action for custom and more advanced configuration.

YAML
steps:-uses:actions/checkout@v5-name:SetupJDK17uses:actions/setup-java@v4with:java-version:'17'distribution:'temurin'cache:maven-name:BuildwithMavenrun:mvn--batch-mode--update-snapshotsverify

This workflow will save the contents of your local Maven repository, located in the.m2 directory of the runner's home directory. The cache key will be the hashed contents ofpom.xml, so changes topom.xml will invalidate the cache.

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.

Maven will usually create output files like JARs, EARs, or WARs in thetarget directory. To upload those as artifacts, you can copy them into a new directory that contains artifacts to upload. For example, you can create a directory calledstaging. Then 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'-run:mvn--batch-mode--update-snapshotsverify-run:mkdirstaging&&cptarget/*.jarstaging-uses:actions/upload-artifact@v4with:name:Packagepath:staging
[8]ページ先頭
©2009-2025 Movatter.jp