Files
bermudalamb ae8f0eb12c
SonarQube Analysis / sonarqube (pull_request) Successful in 3m52s
Tests / lint (pull_request) Successful in 1m55s
Tests / backend-unit (pull_request) Successful in 46s
Tests / frontend-e2e (pull_request) Failing after 9m41s
fix(ci): make SonarQube actually analyse the frontend (#67)
SonarQube was analysing none of frontend/src. All 34 files were indexed and reported ncloc 0, so the quality gate had been measuring roughly a third of the codebase while appearing to cover it. The scanner log gives the cause: frontend/tsconfig.json sets "moduleResolution": "bundler", which is correct for Vite, and the TypeScript bundled with SonarQube 9.9 predates 5.0 and rejects it. Building the frontend program throws, every frontend file is dropped, and the scan still exits EXECUTION SUCCESS — which is why a green job hid this indefinitely.

Adds frontend/tsconfig.sonar.json, an analysis-only mirror that differs only in using "node", and points the scan at it via sonar.typescript.tsconfigPaths. The app's own tsconfig is deliberately untouched: "bundler" is right for the build, and changing it to satisfy an old analyser would let the tool dictate the build. The mirror cannot use `extends` — the old compiler validates the base file while reading it, so the error just moves to pointing at tsconfig.json.

Verified locally against a scratch project: 59/59 files analysed, no skips. Analysed lines go from 2,069 to 5,481, code smells from 2 to 14, security hotspots from 3 to 4, and technical debt from 21 to 85 minutes. The frontend had been hiding twelve code smells and a hotspot, which is part of why the React problems behind #60 and #62 had to be found by hand.

A standalone copy drifts, and drift here does not fail anything — it silently returns to skipping the frontend while reporting success. scripts/check-sonar-tsconfig.js compares the two and fails when they diverge in anything but moduleResolution, and runs before the scan so the scan is never what discovers it. Confirmed it catches drift by introducing some.

Moves scan settings into sonar-project.properties at the repo root so a local scan and the CI scan analyse the same thing, leaving only the host and token in secrets. Adds scripts/scan-local.sh, which runs the scanner in Docker because it needs Java 11+ and the dev machine has Java 8, and which defaults to a scratch project key: the server is Community edition with no branch analysis, so any scan overwrites the single main analysis of whichever key it is given.

Closes #67
2026-08-19 14:50:20 -05:00

50 lines
1.8 KiB
Bash

#!/usr/bin/env bash
# Run a SonarQube analysis from this machine, using the same
# sonar-project.properties that CI uses.
#
# Publishes to a SCRATCH project key by default, and that default is the point
# of this script. The server is SonarQube Community, which has no branch
# analysis: every scan overwrites the single "main" analysis of whatever project
# key it is given. Scanning a feature branch under the real key would replace
# CI's picture of main with your working tree, silently.
#
# ./scripts/scan-local.sh # -> redefined-designs-local
# ./scripts/scan-local.sh redefined-designs # -> the real project, deliberate
#
# Needs SONARQUBE_URL and SONARQUBE_TOKEN in the environment, and Docker. The
# scanner runs in a container because it needs Java 11+, and the Java on the dev
# machine is 8.
set -euo pipefail
PROJECT_KEY="${1:-redefined-designs-local}"
REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
if [[ -z "${SONARQUBE_URL:-}" || -z "${SONARQUBE_TOKEN:-}" ]]; then
echo "SONARQUBE_URL and SONARQUBE_TOKEN must be set." >&2
exit 1
fi
if [[ "$PROJECT_KEY" == "redefined-designs" ]]; then
echo "Publishing to the REAL project — this replaces CI's analysis of main until the next CI run."
echo "Ctrl-C within 5s to abort."
sleep 5
fi
# Docker needs a Windows-style path here; MSYS_NO_PATHCONV stops Git Bash
# rewriting the container-side path.
HOST_PATH="$REPO_ROOT"
if [[ "$(uname -s)" == MINGW* || "$(uname -s)" == MSYS* ]]; then
HOST_PATH="$(cd "$REPO_ROOT" && pwd -W)"
fi
echo "Scanning $HOST_PATH -> $PROJECT_KEY on $SONARQUBE_URL"
MSYS_NO_PATHCONV=1 docker run --rm \
-e SONAR_HOST_URL="$SONARQUBE_URL" \
-e SONAR_TOKEN="$SONARQUBE_TOKEN" \
-v "$HOST_PATH:/usr/src" \
sonarsource/sonar-scanner-cli:5 \
-Dsonar.projectKey="$PROJECT_KEY" \
-Dsonar.working.directory=/tmp/scannerwork \
"${@:2}"