← All insightsProduction

Running SonarQube in production: a hardening checklist

CodeWizard Engineering · 24 October 2025 · 3 min read · Advanced

Demos and production are different sports. This checklist covers what changes when SonarQube has to be reliable, secure and observable under real load.

Security and reliability defaults

  • Treat vulnerabilities and hotspots as gating, not advisory
  • Keep tokens scoped and rotate them

A production-minded config

Project configuration file.

properties
# sonar-project.properties
sonar.projectKey=acme-web
sonar.sources=src
sonar.tests=test
sonar.javascript.lcov.reportPaths=coverage/lcov.info
sonar.qualitygate.wait=true

Operational best practices

  • Enforce a 'new code' Quality Gate on every PR
  • Wire coverage reports into the scan
  • Triage security hotspots, don't blanket-ignore them
In production, boring and reproducible beats clever every time.

Want 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.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult