![]() You can also add this workflow manually by creating a new file in the. ![]() For more information, see the " Quickstart for GitHub Actions." To get started quickly, you can choose the preconfigured Gradle starter workflow when you create a new workflow. For more information, see the Gradle starter workflow. GitHub provides a Gradle starter workflow that will work for most Gradle-based Java projects. For more information, see " Setting up the tool cache on self-hosted runners without internet access." Using the Gradle starter workflow When using setup actions (such as actions/setup-LANGUAGE) on GitHub Enterprise Server with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. Using self-hosted runners on GitHub Enterprise Server ![]() For more information, see Getting Started in the Gradle documentation. We recommend that you have a basic understanding of Java and the Gradle framework. You should be familiar with YAML and the syntax for GitHub Actions. ![]() For a list of software and the pre-installed versions for JDK and Gradle, see " About GitHub-hosted runners". GitHub-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Gradle. You can extend your CI workflow to cache files and upload artifacts from a workflow run. 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. This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Gradle build system. You can see more information about planned future support on the GitHub public roadmap. Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server.
0 Comments
Leave a Reply. |