SonarQube won't scan any project files

SonarQube for IDE IntelliJ Platform
,
1
  • Operating system: Windows 11
  • SonarLint plugin version: 10.14.1.80220
  • IntelliJ version: CLion 2024.3.1.1
  • Programming language you’re coding in: C
  • Is connected mode used: No

On IDE startup SonarQube only scans the CMake file, here’s the log:

Analysing 'CMakeLists.txt' (ID xxxxxxxxxxx)...
 [2024-12-27T10:11:27.461] [SonarLint Server RPC request executor] INFO sonarlint - Triggering analysis with configuration: [
  baseDir: C:\xxxx\xxxx\PROJECT_ROOT
  extraProperties: {sonar.cfamily.build-wrapper-content={"version":0,"captures":[]}, sonar.js.internal.bundlePath=C:\Users\xxxx\AppData\Roaming\JetBrains\CLion2024.3\plugins\sonarlint-intellij\plugins\eslint-bridge}
  activeRules: [432 cpp, 190 c, 29 secrets]
  inputFiles: [
    file:///C:/xxxx/xxxx/PROJECT_ROOT/CMakeLists.txt (UTF-8)
  ]
]

When I use the analyze all project files, SonarQube only scans the non source code related files like *.s, *.txt, *.cfg, etc.

I’m wondering if I have missed some config to set for SonarQube to work properly, but the older versions of the plugin did’t require any setup. Please let me know. Thanks for your help!

2

Hello @AwsomeTofu, and thanks for reaching out to us!

Could you please share the full SonarQube for IDE logs?

We have different heuristics to decide which files to analyze; this normally includes files that are part of the source content of the project or any file that is not ignored by your git ignore file. Having the logs could help identify the cause.

5

Hello @nicolas.quinquenel ,

I have just figured it out today.
Recently for CLion, JetBrains has updated it’s internal code analysis engine to Nova. And that causes the issue where SonarQube stopped indexing C files. After switching back to the classic engine for CLion, everything works fine.

The issue should be very easy to reproduce. I tested it myself with a fresh install of CLion and switching between the Nova and classic engine, and I can confirm that SonarQube doesn’t work under the Nova engine with a default Hello World project. The classic engine works fine.

image
image401×275 9.12 KB

1 Like
6

Thanks for your reply. This is effectively a known issue for C files when using Nova engine, and we haven’t found a workaround yet.

1 Like
7

Thanks for the info. It might be helpful to include the keyword “Nova Engine” somewhere in the title or the context for that ticket. I came across that issue before, but for CLion users it is not that easy to relate ReShaper and Nova Engine. JetBrains only uses “Nova” to brand that new engine inside CLion. And so far I haven’t found any online info stating directly about this issue with CLion. :pray:

1 Like
8

Thank you for your feedback; it’s very much appreciated. I modified the tickets to include the Nova keyword. I will also check if we can update our documentation to include such cases as known limitations for now.