SonarQube plugin not analyzing file in Clion

SonarQube for IDE IntelliJ Platform
1
  • Operating system: Windows 11
  • SonarQube for IntelliJ plugin version: 11.4.0.82618
  • IntelliJ version: Clion 2025.2
  • Programming language you’re coding in: C++
  • Is connected mode used:
    • SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?): Community Edition Version 10.4.1 (build 88267)

And a thorough description of the problem / question:
I used the SonarQube for IDE to connect our project to my Clion IDE instance.
The connection was made successfully, however, no analysis are being made. One single file, for example, is showing issues in server, but 0 issues in clion plugin.
The project is a C++ with CMake.

I Uploaded the log with verbose mode enabled.

log-clion-sonarqube.txt (233.1 KB)

4

Hey @Vini_42, thank you for reaching out about this.

Could you please share the output of Show compiler info action on the source file you are looking at?

I see that SonarQube for IDE is not able to fetch your C++ compiler information. Are you using any kind of WSL or remote toolchain configuration?

5

Yes, I uploaded

compiler-info.txt (32.2 KB)

I am using MSVC from Visual Studio 2022 with C++23 language version

10

Thank you!

It seems that the analyzer was loaded correctly, but we were unable to load any C/C++ rules. Can you make sure that your project binding is correctly configured and points to the appropriate project?

Also, could you please try analyzing a file after removing the connection to your SonarQube server?

12

I have the same issue with

CLion 2026.2
plugin version 12.6.0.84973
Windows 11
MSVC for c++20

No analyses are carried out, whether bound to our SonarQube project or not.

14

Hi @leon

Could you provide the logs, similar to original poster?

15

Logs:

clion_sonarqube_log.txt (14.9 KB)

compiler_info.txt (13.1 KB)

When I click on “Analyze Current File” or in the file editor from Context Menu “Analyze with SonarQube” nothing happens, no further log output.