Skip to content

SonarQube

SonarQube analyzes code your team owns and can help make a code-quality check part of reviewing changes.

Visit SonarQube

What is a quality gate?

A quality gate is a rule your team uses to decide whether a change passes its automated checks. SonarQube analyzes code and reports findings against configured conditions. Choose a condition a reviewer understands and can act on when it fails.

What changes if your team runs SonarQube itself?

Cloud and Server are separate setups. With Server, your team runs the service and looks after access and updates. The plan page describes lines of code analyzed as a pricing unit for paid private Cloud projects and for Server editions. Check language, repository and edition coverage for your project.

Who should review a reported problem?

Give a developer responsibility for reading the finding in context. Decide which problems should block a release and which need a tracked follow-up. A passing quality gate is one part of release review alongside testing what customers actually do.

Which finding should stop the next release?

On paper, write two fictional findings for a booking app: an unclear name and a reliability issue in saving bookings.

  1. Choose what matters now
    Explain which one merits blocking this release and what the reviewer should check.
  2. Give the other a home
    If it can wait, decide who will revisit it and when.