SonarQube Server Developer Edition was selected and configured in pipeline YAML for C# and SQL analysis, Azure Repos PR decoration, and merge-blocking quality gates. Its documented capabilities fit the security, correctness, EU-hosting, and audit-evidence requirements well.
- What worked
- The documented Azure DevOps tasks and quality-gate model mapped cleanly to PR validation and release-commit scanning, while self-hosting avoided introducing a generative-model data path.
- What got in the way
- No live SonarQube instance or service connection was available, so analysis results, PR decoration, security-hotspot behavior, and gate enforcement could not be exercised.