Most SonarQube pain is self-inflicted and predictable. Here are the mistakes we see most, and the fix for each.
Mistake 1: Analyzing but not enforcing the Quality Gate, so nothing improves
Fix: Enforce a 'new code' Quality Gate on every PR. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
Mistake 2: Chasing a green gate by disabling rules instead of fixing issues
Fix: Wire coverage reports into the scan. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
Mistake 3: No coverage report wired in, so coverage looks like zero
Fix: Triage security hotspots, don't blanket-ignore them. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
A safer baseline
Project configuration file.
# sonar-project.properties
sonar.projectKey=acme-web
sonar.sources=src
sonar.tests=test
sonar.javascript.lcov.reportPaths=coverage/lcov.info
sonar.qualitygate.wait=trueWant senior help putting SonarQube to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.