← All insightsConcepts

SonarQube: core concepts and configuration explained

CodeWizard Academy · 26 October 2025 · 3 min read · Beginner

Continuous code quality and security analysis with quality gates that block risky merges. This walkthrough covers the mental model and the configuration you will actually touch.

SonarQube statically analyzes code for bugs, vulnerabilities, security hotspots and 'code smells', and enforces a Quality Gate in CI so problematic changes fail the build.

The configuration that matters

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

Principles to hold onto

  • Enforce a 'new code' Quality Gate on every PR
  • Wire coverage reports into the scan
  • Triage security hotspots, don't blanket-ignore them

Everyday commands

bash
sonar-scanner -Dsonar.host.url=http://localhost:9000 -Dsonar.token=$SONAR_TOKEN

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