Add SonarQube scan workflow
All checks were successful
SonarQube Scan / SonarQube Trigger (push) Successful in 18m19s

This commit introduces a Gitea workflow to trigger
SonarQube scans on pushes to the `main` branch and
on pull requests.
This commit is contained in:
2025-07-19 00:04:19 +02:00
committed by Christian Basler
parent 1836f53d7b
commit 1527ab0cb0
3 changed files with 52 additions and 1 deletions

View File

@@ -0,0 +1,42 @@
on:
push:
branches:
- main
pull_request:
types: [opened, synchronize, reopened]
name: SonarQube Scan
jobs:
sonarqube:
name: SonarQube Trigger
runs-on: ubuntu-latest
steps:
- name: Checking out
uses: actions/checkout@v4
with:
# Disabling shallow clone is recommended for improving relevancy of reporting
fetch-depth: 0
- name: Set up JDK 21
uses: actions/setup-java@v4
with:
java-version: 21
distribution: 'temurin' # Alternative distribution options are available.
- name: Setup Android SDK
uses: android-actions/setup-android@v3
- name: Cache SonarQube packages
uses: actions/cache@v4
with:
path: ~/.sonar/cache
key: ${{ runner.os }}-sonar
restore-keys: ${{ runner.os }}-sonar
- name: Cache Gradle packages
uses: actions/cache@v4
with:
path: ~/.gradle/caches
key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }}
restore-keys: ${{ runner.os }}-gradle
- name: SonarQube Scan
env:
SONAR_TOKEN: ${{ secrets.SONARQUBE_TOKEN }}
SONAR_HOST_URL: ${{ secrets.SONARQUBE_HOST }}
run: ./gradlew build sonar --info --build-cache