I am a beginner, I was working on a CI pipeline, there I am getting sonar coverage issue. Source code path is not picking by sonar and not getting coverage. But it’s picking the test path files correctly and reporting in dashboard. [IMG20240205212358]

Hey Ann, Issue is fixed now… Sonar.exclusion was the root cause… this excluded all necessary files/classes required for src code, that’s why it’s not analysing the source code. Now i can see the stats in sonar UI. now reworking with developer for correct exclusions…

Jacoco.xml is generating,but sonar coverage is 0%

SonarQube Server / Community Build

ganncamp (G Ann Campbell) Split this topic February 7, 2024, 12:46pm 5

A post was split to a new topic: JaCoCo coverage not generated

Topic		Replies	Views
Local jacoco code coverage % and sonarqube coverage % is different, why? SonarQube Server / Community Build sonarqube , scanner , coverage , jacoco , bump	20	1948	April 9, 2024
Sonarqube not showing code coverage SonarQube Server / Community Build	3	5609	August 31, 2020
Jacoco xml report imported but coverage still 0% SonarQube Server / Community Build java , sonarqube , jacoco	8	7610	September 23, 2020
Code coverage is showing 0 SonarQube Server / Community Build coverage	12	740	July 11, 2022
Code Coverage and Unit Tests are not showing up in the Sonarqube SonarQube Server / Community Build sonarqube , jenkins , coverage , unit-test	8	17196	May 17, 2023

Jacoco.xml is generating,but sonar coverage is 0%

Related topics