Mirrors the website repo's setup: a source-based scan of sidecar/src that reports to the self-hosted SonarQube server after merge, never gating PRs. Uses the existing SonarQube project key Runic-Gateway-link (the server rejects re-creating a case-variant key). Supersedes #13. Co-Authored-By: Claude <noreply@anthropic.com>
26 lines
1.2 KiB
Properties
26 lines
1.2 KiB
Properties
# SonarQube analysis config for the link (uo-link sidecar) repo.
|
|
# Consumed by the scanner in .gitea/workflows/sonarqube.yml on push to main.
|
|
# The project key must match the one created in SonarQube (dashboard URL
|
|
# ?id=Runic-Gateway-link).
|
|
|
|
sonar.projectKey=Runic-Gateway-link
|
|
sonar.projectName=runic gateway link
|
|
|
|
# Analysed application code. The Rust sidecar crate lives under sidecar/src.
|
|
# Rust unit tests live inline (#[cfg(test)] modules) rather than in a separate
|
|
# tree, so there is no distinct sonar.tests path to declare.
|
|
sonar.sources=sidecar/src
|
|
|
|
# Never analyse build output, the vendored lockfile, or generated config.
|
|
sonar.exclusions=**/target/**,**/*.lock
|
|
|
|
sonar.sourceEncoding=UTF-8
|
|
|
|
# ── Optional enrichment (enable if your SonarQube edition/version supports it) ──
|
|
# SonarQube imports Clippy findings when given a JSON report. To turn this on:
|
|
# 1. In sonarqube.yml, add a step before the scan that runs:
|
|
# cargo clippy --message-format=json > sidecar/clippy-report.json
|
|
# (needs the Rust toolchain + `rustup component add clippy` on the runner).
|
|
# 2. Uncomment the line below.
|
|
# sonar.rust.clippy.reportPaths=sidecar/clippy-report.json
|