SonarLint Connected Mode

SonarLint Connected Mode connects SonarLint to your SonarQube project and provides additional benefits you won’t get by using SonarLint or SonarQube alone.

SonarLint’s Connected Mode connects SonarLint to your SonarQube project and provides additional benefits you won’t get by using SonarLint or SonarQube alone.

Shared code quality and security expectations When using SonarLint , the Sonar way Quality Profile is used by default and users can customize their ruleset. If you’re using a different quality profile in SonarQube, new issues might be raised in SonarQube even though your commit looked clean in SonarLint. With Connected Mode, the same customized rule set is applied in both your IDE and in SonarQube, and you’re notified in your IDE when your local instance isn’t meeting the project’s Quality gates standards.

More security When using SonarLint alone, taint analysis issues found by commercial editions of SonarQube aren’t raised in SonarLint for performance reasons (we don’t want to slow down your editing). In Connected Mode, you’ll see the taint analysis issues SonarQube raised in your project. You’ll get all of the context in your IDE that you need to triage and fix security problems thereby making sure the code you commit is safe.

Setting up Connected Mode

See the following links for instructions on setting up Connected Mode for each supported IDE:

• Connected mode

• Connected mode

• Connected mode

• Connected mode

Smart notifications

Connected Mode allows SonarQube to send smart alerts to individuals or teams when new issues are discovered. With everyone in the loop, issues can be addressed promptly, improving the overall software quality and delivery. You’ll receive smart notifications in your IDE when:

• the Quality gates status of a project open in your IDE changes

• a SonarQube analysis raises new issues that you’ve introduced in a project open in your IDE

You can activate or deactivate smart notifications in SonarLint on the IDE side on a server-by-server basis.