Connected mode

Using connected mode in SonarQube for IntelliJ completes the Sonar Solution to make the most of your analyses. Running in connected mode helps bring SonarQube's AI capabilities into your IDE.

Connecting SonarQube for IDE to SonarQube Server, SonarQube Cloud, or SonarQube Community Build is the first step in setting up the Sonar Solution, to take advantage of having consistent issues reported on both sides. Setting up connected mode will permit the transmission of information SonarQube for IDE needs, such as URLs and user credentials or file exclusions and marked issues, to communicate with SonarQube (Server, Cloud) or SonarQube Community Build. When binding your local workspace folder to your SonarQube (Server, Cloud) or SonarQube Community Build project(s), SonarQube for IDE will try to match, as much as possible, the same rules and settings as found on the server.

While in connected mode, SonarQube for IDE receives notifications from SonarQube (Server, Cloud) or SonarQube Community Build about your quality gate changes and new issues. Smart notifications can be enabled or disabled from the UI while creating or editing the connection settings.

Benefits

  • Analyze more languages and detect more issues by combining rules in the IDE with those supported by SonarQube (Server, Cloud), or Sonarqube Community Build.

  • Highlight advanced issues (in the IDE) like Injection vulnerabilities, detected by SonarQube (Server, Cloud).

  • An issue discovered in SonarQube (Server, Cloud) or SonarQube Community Build can be quickly explored in the IDE via a dedicated button. See the Opening issues in the IDE article for details.

  • Use the same quality profile locally as is defined by SonarQube (Server, Cloud), or SonarQube Community Build.

  • Apply settings, such as Rule selection and File exclusions defined on the server to your local analysis.

  • Define specific analyzer parameters on the server and have those parameters applied locally.

  • Automatically suppress issues that are marked as Accepted or False Positive on the server. See the Marking issues article to understand how this works locally.

When running in connected mode with SonarQube Server 10.4 or newer, Won’t Fix becomes Accept.

  • Use the SonarQube for IntelliJ Focus on new code feature to concentrate the detection of issues only in new code, as you defined in SonarQube (Server, Cloud), or SonarQube Community Build.

    • See the Focusing on new code article

    • Check the page on New code for information about how it affects quality standards locally and on the server.

  • When you accept Notifications in your IDE, changes made to your quality gates on the server arrive in your IDE.

Connected mode does not push issues to the server. Rather, its purpose is to configure the IDE so that it uses the same settings, as much as possible, as it is defined on the server.

Free and open-source versions of SonarQube Community Build and SonarQube Cloud are available to work in connected mode. In SonarQube Cloud, it’s always free to analyze your publicly accessible projects; if you want to link to a private repository, see the instructions found on SonarQube Cloud's Subscription plans page.

Prerequisites and supported languages

To run SonarQube for IntelliJ in connected mode, you must have a SonarQube Server project in an active version (see the Release cycle model page) or a SonarQube Cloud project.

In addition to the published languages listed on the Rules and languages page, you can unlock Scala, Swift, and PL/SQL rules when using connected mode.

Branch awareness

Branch awareness allows SonarQube for IDE to consider the branch currently checked out in the IDE and synchronize it with the most appropriate branch from the SonarQube (Server, Cloud) or SonarQube Community Build; we call this branch matching.

In Connected Mode, SonarQube for IDE synchronizes some data from the issues found on the server, such as the issue’s status and resolution. It is important that SonarQube for IDE knows which branch the user is on at that moment to sync the local analysis with the correct branch analyzed by SonarQube (Server, Cloud) or SonarQube Community Build.

SonarQube for IntelliJ only supports git and the git branch name with regard to branch matching, using the git4idea client shipped by JetBrains. If SonarQube for IDE’s branch awareness algorithm fails to detect a best match, Injection vulnerabilities and issue suppressions will be pulled from the main branch by default.

Checking which branches are analyzed on the server

In SonarQube Server, open the highlighted drop-down list shown below (as it looks in SonarQube Server) for a list of analyzed branches and pull requests.

A view of your analyzed branches and pull request in SonarQube Server.

To analyze branches other than master|main , please check these pages on branch analysis:

How SonarQube for IDE selects which branch to sync

SonarQube for IDE deploys these three methods to choose which branch (in SonarQube (Server, Cloud)) to sync with the local analysis.

Exact match

Branches with the same name are considered the same branch. If the branch that is currently checked out locally is analyzed on the server, SonarQube for IDE will pick this branch for synchronization.

Closest branch

SonarQube for IDE will consider all local branches that also exist on the server. For each branch, SonarQube for IDE will compute the distance between the current HEAD and the branch by the count of commits. The closest branch will be kept. In case the number of commits is the same for two or more branches and the main branch is among them, the main branch will be preferred; otherwise, the tie will be broken with a random choice (from the list of equidistant branches).

Default to main branch

All other cases will default to the branch marked as "main" on the server. For example, if there is an error in reading the branch, or if there is no Git repo, SonarQube for IDE will default to the main branch.

Long and short-lived branches

When using Connected Mode with SonarQube Cloud, issues on short-lived branches are not synchronized. When an issue is marked in SonarQube Cloud accepted or false positive on a short-lived branch, SonarQube for IDE will still show that issue in the IDE.

SonarQube Server does not distinguish between long- and short-lived branches therefore, all issue resolutions are recognized.

Connection setup

SonarQube for IntelliJ provides a connection wizard to help you set up connected mode with SonarQube (Server, Cloud). Please see the Connected mode setup page for detailed instructions to set up connected mode and bind your project.

Sharing your setup

From version 10.5, you can share a setup configuration file with your team, simplifying the process.

One team member must step through the first-time setup process, then export and commit the binding configuration to the repository. Any team member running SonarQube for IDE will find the binding details inside of the project’s source folder and automatically receive a notification to bind the project.

Please see the Connected mode setup page for detailed instructions.

Troubleshooting connected code

See the Troubleshooting page for details to look at when your SonarQube for IDE analysis does not match what you see in SonarQube (Server, Cloud).

SonarQube for IDE-SonarQube Server version support policy

SonarQube for IDE enables users to establish a connection to the latest SonarQube Server version and to the latest LTA (Long-Term Active) version. When a new LTA version is released, we still enable connecting SonarQube for IDE to the previous LTA version for a certain period of time (currently 9 months after the latest LTA release) to allow enough time for organizations to update their SonarQube Server version.

For more information about long-term support of SonarQube Server, check out our page describing SonarQube Server's Release cycle model. Review your SonarQube for IDE-specific requirements for version-to-version differences.

The 8.9LTA reached its support expiration date (in November ’23).

Notifications

Connected mode allows SonarQube (Server, Cloud) and SonarQube Community Build to send smart alerts to individuals or teams as soon as something appears on the server that something failed, when new issues are discovered or when the Sonar Quality Profile is updated, for example. With everyone in the loop, issues can be addressed promptly, improving the overall software quality and delivery. The notification will include a link to call back to SonarQube (Server, Cloud) and SonarQube Community Build where you can learn more about the issues that were introduced.

You’ll receive smart notifications in your IDE when:

  • the quality gate status of a project you have open in your IDE changes. See these pages on managing quality gates:

  • a SonarQube (Server, Cloud) and SonarQube Community Build analysis raises new issues that you’ve introduced in a project open in your IDE

Sonar Smart Notifications are available in all editions of SonarQube (Server, Cloud) and SonarQube Community Build. You can activate or deactivate smart notifications in SonarQube for IDE on the IDE side for a server-by-server basis.

PreviousTeam featuresNextConnected mode setup

Last updated

Was this helpful?