setup-java VS setup-dotnet

name: Java Build and Test With Gradle on: [push, pull_request, workflow_dispatch] jobs: build: runs-on: ubuntu-latest permissions: contents: read steps: - name: Checkout uses: actions/checkout@v4.2.2 with: fetch-depth: 0 - name: Set up JDK 23 uses: actions/setup-java@v4.5.0 #https://github.com/actions/setup-java with: java-version: '23' distribution: 'oracle' - name: Install GitVersion 6.0.5 for Gradle run: | wget -q -O gitversion.tar.gz https://github.com/GitTools/GitVersion/releases/download/6.0.5/gitversion-linux-x64-6.0.5.tar.gz mkdir gitversion_extracted tar -xzf gitversion.tar.gz -C gitversion_extracted ls -R gitversion_extracted sudo mv gitversion_extracted/gitversion /usr/local/bin/gitversion sudo chmod +x /usr/local/bin/gitversion - name: Setup Gradle 8.11.1 uses: gradle/actions/setup-gradle@v4 #https://github.com/gradle/actions/blob/main/docs/setup-gradle.md#build-with-a-specific-gradle-version with: gradle-version: '8.11.1' - name: Build with Gradle 8.11.1 run: gradle build --scan --warning-mode all dependency-submission: # See: https://github.com/gradle/actions/blob/main/dependency-submission/README.md runs-on: ubuntu-latest permissions: contents: write steps: - name: Checkout uses: actions/checkout@v4.2.2 - name: Set up JDK 23 uses: actions/setup-java@v4.5.0 with: java-version: '23' distribution: 'oracle' - name: Setup Gradle 8.11.1 uses: gradle/actions/setup-gradle@v4 with: gradle-version: '8.11.1' - name: Setup Gradle Wrapper run: gradle wrapper - name: Generate and submit dependency graph uses: gradle/actions/dependency-submission@v4

Then, we have two important initial steps to define. The first one is an official GitHub Action used to check-out a repository so a workflow can access it. The second one it's pretty more complex but, briefly, downloads and set up a requested version of Java.

The most popular ones are Node.js, Python, Java JDK, Go, .Net Core SDK.

Finally, note that the v2 of setup-java GitHub Action limits the possible JDK distributions to four options. If you need to use one that is not listed, use foojayio/setup-java instead to configure any distribution.

See https://github.com/actions/setup-java for more configuration regarding distribution, version and caching.

Why can't Oracle just integrate with https://github.com/actions/setup-java like everyone else?

Next up we'll need to add a step to compile our production ready build. For this we can add two new steps, one which configures our Node version to ensure it matches our application, followed by another that runs the necessary commands with npm. Depending on how your application is built you may need to add another step between these to install any sort of required environments such as Python or Java.

Set up the JDK with the actions/setup-java GitHub Action.

# This workflow will build a .NET project # For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-net name: .NET Build and Test on: [push, pull_request, workflow_dispatch] jobs: build_and_Test: runs-on: ubuntu-latest steps: - name: Checkout #https://github.com/GitTools/actions/blob/main/docs/examples/github/gitversion/setup.md uses: actions/checkout@v4 with: fetch-depth: 0 - name: Install GitVersion #https://github.com/GitTools/actions/blob/main/docs/examples/github/gitversion/setup.md uses: gittools/actions/gitversion/setup@v3.0.0 with: versionSpec: '6.x' preferLatestVersion: true - name: Determine Version #https://github.com/GitTools/actions/blob/main/docs/examples/github/gitversion/execute.md uses: gittools/actions/gitversion/execute@v3.0.0 with: useConfigFile: true updateAssemblyInfo: true - name: Setup .NET #https://github.com/actions/setup-dotnet uses: actions/setup-dotnet@v4 - name: Available projects run: dotnet sln list - name: Restore dependencies run: dotnet restore - name: Build run: dotnet build --no-restore - name: Test run: dotnet test --no-build --verbosity normal

The most popular ones are Node.js, Python, Java JDK, Go, .Net Core SDK.

Setup Dotnet

The second step will set up .NET on the runner. Here I have specified to install the latest version of 3.1. We are using the GitHub action project setup-dotnet to complete the installation on the runner.

Your question isn't really about whether GitHub Actions support .NET 5, but more about whether the setup-dotnet GitHub Action supports .NET 5 since it is that action that you are using to install the necessary .NET tools to build your project. Here is a link to the setup-dotnet GitHub Action and it's documentation.

This workflow is executed whenever a commit is pushed to the 'main' branch. The single job called 'build_and_deploy' is run on an Ubuntu machine. This machine has some software pre-installed. Today the 'ubuntu-latest' image comes with the .NET 5 SDK pre-configured, but at the time you are reading this, the SDK version could be a newer version. You can use the 'setup-dotnet' GitHub Action to setup a different version of .NET, or to ensure the version of the SDK will be the version specified even when the 'ubuntu-latest' image is updated to use newer versions of .NET.