Problem with No coverage on Sonaqube Console

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension) → Sonarqube Server Data Center Edition

    v2025.1.2 (108896)

  • how is SonarQube deployed: Jenkins pipeline

  • what are you trying to achieve → Show coverage on Sonar Console.

  • what have you tried so far to achieve this→ i was able to get coverage by using commands

  • It create the next info.

  • 15:01:40  =============================== Coverage summary ===============================
15:01:40  Statements   : 41.88% ( 62155/148398 )
15:01:40  Branches     : 34.44% ( 37129/107805 )
15:01:40  Functions    : 26.79% ( 10356/38651 )
15:01:40  Lines        : 52.37% ( 52041/99365 )
15:01:40  ================================================================================

but console showed me “Coverage Not computed **60.4%**Estimated after merge”

also in the Sonar Scan stage i found

15:13:16  INFO: ------------- Run sensors on project
15:13:16  INFO: Sensor Zero Coverage Sensor
15:13:16  INFO: Sensor Zero Coverage Sensor (done) | time=8ms

The folder coverage was created and file

Shell Script – ls -l coverage/lcov.info (self time 442ms)

15:12:20  + ls -l coverage/lcov.info
15:12:20  -rw-r--r-- 1 jenkins jenkins 4331818 Sep 29 21:01 coverage/lcov.info

Please some guidance here!

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

4

Hey there.

In that case it sounds like coverage import is working correctly, but coverage “isn’t computed” because in your PR, you’re only changing config files (not source code that can be covered by tests)

5

Hi Thanks for your fast response I really appreciate it. Question, right now we just have coverage on main branches but not in PR, how can i force it to have full coverage also on PR ?

Thanks

6

The Esimated after merge figure is indeed what the coverage will be on the main branch if you merge the code. If you’re talking about something else, I’m not sure I understand.