GitHub Actions

Every repository within the CoMPAS GitHub organization need a default set of GitHub Actions. GitHub Actions are CI/CD steps within a GitHub Repository that you can configure. This way, you can ensure that certain steps (like building) are always triggered on for example a commit push.

Within CoMPAS, we define the following ‘must have’ GitHub Actions:

• Building
• REUSE check
• SonarCloud
• Docker Hub Deployment

More to follow.

GitHub Actions are configured using YAML files. These files are stored in the .github/workflows directory of a specific repository.

REUSE check

For keeping our copyright and licensing information up to date and correct, we use REUSE to check this. This is also configured for every separate repository in an easy manner: just create a reuse.yml file in the .github/workflows directory containing the following source code:

name: REUSE Compliance Check

on: push #(1)

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: REUSE Compliance Check
      uses: fsfe/reuse-action@v1

A few points to remember:

• (1): By default, all actions are triggered on a push action.

This is the only thing that has to be done. After this, it will be checked on every push.

REUSE badge

For transparency, CoMPAS repositories also include a REUSE badge in their README for fast checking the REUSE compliance.

Two steps are needed to get a REUSE badge to work:

1. Register the Repository at the REUSE website. For name and email, check the Slack channel.
2. Add the following code to the README:

[![REUSE status](https://api.reuse.software/badge/github.com/com-pas/repoName)](https://api.reuse.software/info/github.com/com-pas/repoName)

There is one steps left: Replace repoName with the name of the specific repository (as stated in the URL).

After doing all these steps, everything is set up for the REUSE check.

SonarCloud

For static code analysis, CoMPAS is using SonarCloud. To configure this, there are several steps that needs to be done.

1. Go to the CoMPAS GitHub organization settings, and click on “Installed GitHub Apps”. SonarCloud is listed here already (because we are already using it). Click on the ‘configure’ button next to it.
2. In the “Repository access” section, select the repository you want to add. By default, not every repository is added as an extra check.
3. Create a new project in SonarCloud.
4. Select the repository to be analyzed, click Set Up.
5. Choose the Analysis Method “With GitHub Actions”.
6. It first tells you to create a SONAR_TOKEN secret in your repo. Go to your repository -> Settings - Secrets -> New repository secret -> Name: SONAR_TOKEN. Value: Copy the value from the SonarCloud website into here. Then save the secret
7. Select Maven as the option that best describes our build and remember the projectKey. and create a sonarcloud_analysis.yml file in the .github/workflows directory containing the following source code running.

name: SonarCloud Analysis

on: push #(1)

jobs:
  build:
    name: Build
    runs-on: ubuntu-latest
    timeout-minutes: 15

    steps:
      - uses: actions/checkout@v2
        with:
          fetch-depth: 0
      - name: Set up JDK 1.11
        uses: actions/setup-java@v2.3.0
        with:
          distribution: 'zulu'
          java-version: '11'
      - name: Cache SonarCloud packages
        uses: actions/cache@v2.1.6
        with:
          path: ~/.sonar/cache
          key: $-sonar
          restore-keys: $-sonar
      - name: Cache Maven packages
        uses: actions/cache@v2.1.6
        with:
          path: ~/.m2
          key: $-m2-$
          restore-keys: $-m2
      - name: Create custom Maven Settings.xml #(2)
        uses: whelk-io/maven-settings-xml-action@v18
        with:
          output_file: custom_maven_settings.xml
          servers: '[{ "id": "github-packages-compas", "username": "OWNER", "password": "$" }]'
      - name: Build and analyze
        env:
          SONAR_TOKEN: $
        run: | #(3)
          mvn -s custom_maven_settings.xml -B -Psonar \
          -Dsonar.projectKey=<insert project key> \
          -Dsonar.organization=com-pas \
          -Dsonar.host.url=https://sonarcloud.io \
          verify org.sonarsource.scanner.maven:sonar-maven-plugin:sonar

A few points to remember:

• (1): By default, all actions are triggered on a push action.
• (2): Creates a custom settings.xml having the credentials for the GitHub Packages. For more information, check our Contributing.
• (3): Replace the <insert project key> with the project key you copied.

Once this is set, it’s all done!

Docker Hub Deployment

For automatic deployment of our microservices, CoMPAS uses Docker Hub as the central docker image repository. This way, all Docker images can be pulled from a central image repository.

This step is easy to configure. Just create a dockerhub_deployment.yml file in the .github/workflows directory containing the following source code:

name: Docker Hub Deployment

on:
  release:
    types: [released] #(1)

jobs:
  push_to_registry:
    name: Build and publish
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Login to Docker Hub #(2)
        uses: docker/login-action@v1
        with:
          username: $
          password: $
      - name: Extract tag name #(3)
        id: extract_tagname
        shell: bash
        # Extra the tagname form the git reference, value of GITHUB_REF will be something like refs/tags/<tag_name>.
        run: echo "##[set-output name=tagname;]$(echo ${GITHUB_REF##*/})"
      - name: Set up JDK 11
        uses: actions/setup-java@v2.3.0
        with:
          distribution: 'zulu'
          java-version: '11'
      - name: Create custom Maven Settings.xml
        uses: whelk-io/maven-settings-xml-action@v18
        with:
          output_file: custom_maven_settings.xml #(4)
          servers: '[{ "id": "github-packages-compas", "username": "OWNER", "password": "$" }]'
      - name: Set version with Maven
        run: mvn -B versions:set -DprocessAllModules=true -DnewVersion=$
      - name: Deploy with Maven to GitHub Packages and Docker Hub #(5)
        run: ./mvnw -B -s custom_maven_settings.xml -Prelease,native clean deploy

A few points to remember:

• (1): By default, the docker image is only deployed on release. This way we have a strict deployment flow, and versions always have the same content. For more information about types of releases, check the GitHub Actions documentation.
• (2): Before deploying to Docker Hub, we need to login first. This can be done by executing a GitHub Action. In this example, DOCKER_HUB_USERNAME and DOCKER_HUB_PASSWORD are used, which are secrets stored at CoMPAS organization. For more information about the username and password, ask in the the Slack channel.
• (3): Extract the tag name from Git and use that as version to be set with Maven ($).
• (4): Creates a custom settings.xml having the credentials for the GitHub Packages. For more information, check our Contributing.
• (5): Building and publishing the docker image is build tool / framework specific. By default, CoMPAS services are using Quarkus and Maven. Deploying to Docker Hub is quite easy using Quarkus and maven, it’s just a matter of building in combination with setting some properties. In this example, we use the quarkus-profile parameter instead of including all the parameters. This way, we can define profile specific properties in our application.properties file (For more information about this, check our Docker Hub Deployment page):

%publishNativeImage.quarkus.native.container-build=true
%publishNativeImage.quarkus.container-image.build=true
%publishNativeImage.quarkus.container-image.group=lfenergycompas
%publishNativeImage.quarkus.container-image.name=compas-scl-data-service
%publishNativeImage.quarkus.container-image.push=true