Issue with Test Coverage Reporting for Branches on GitLab with Spring Boot 3.3.0

[Nik2 (Nikita H)]

Hello!
After upgrading version of Spring Boot from 3.2.8 to 3.3.0 we stopped having any coverage related information for our branches. We checked the project build and for the both versions it is the same.

Software Version

Spring Boot 3.3.0
sonarqube-community-branch-plugin 1.8.0
Jacoco 0.8.9
Gradle 8.3
SonarQube 10.3-community
Java 17
CI: GitLab

Is there a way to replicate the previous behavior for current setup?

[Colin]

What do the logs say about importing code coverage?

How to find logs about importing code coverage

When coverage data isn’t appearing as expected in SonarQube / SonarCloud, the first place you should look is the scanner logs. Where do I find the scanner logs? This will likely be broken out into its own guide soon The Scanner logs are the output of executing one of the scanners, either directly or wrapped by one of many integrations, such as the SonarScanner for Jenkins, SonarScanner for Azure DevOps, SonarQube/SonarCloud GitHub Actions or SonarQube / SonarCloud Bitbucket Pipes. …

How are the logs different (are the logs different?) from your previous builds where coverage was reported?

[Nik2 (Nikita H)]

@Colin

What do the logs say about importing code coverage?

The configuration :detachedConfiguration462 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :detachedConfiguration462 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
...
2024-07-25T15:25:01.295+0200 [DEBUG] [org.sonarqube.gradle.SonarTask] Sensors : JaCoCo XML Report Importer -> Kotlin Sensor -> Gradle Sensor -> KotlinSurefireSensor -> CSS Rules -> C# Project Type Information -> C# Analysis Log -> C# Properties -> HTML -> TextAndSecretsSensor -> VB.NET Project Type Information -> VB.NET Analysis Log -> VB.NET Properties -> com.github.mc1arke.sonarqube.plugin.scanner.ScannerPullRequestPropertySensor -> IaC Docker Sensor
2024-07-25T15:25:01.295+0200 [INFO] [org.sonarqube.gradle.SonarTask] Sensor JaCoCo XML Report Importer [jacoco]
2024-07-25T15:25:01.301+0200 [INFO] [org.sonarqube.gradle.SonarTask] Importing 1 report(s). Turn your logs in debug mode in order to see the exhaustive list.
2024-07-25T15:25:01.301+0200 [DEBUG] [org.sonarqube.gradle.SonarTask] Reading report '/home/admin/workspace/project/build/reports/jacoco/test/jacocoTestReport.xml'
2024-07-25T15:25:01.329+0200 [DEBUG] [org.sonarqube.gradle.SonarTask] 'src/main/kotlin/com/app/backend/service/CrudService.kt' generated metadata with charset 'UTF-8'
...
2024-07-25T15:25:01.506+0200 [INFO] [org.sonarqube.gradle.SonarTask] Sensor JaCoCo XML Report Importer [jacoco] (done) | time=211ms
2024-07-25T15:25:01.506+0200 [INFO] [org.sonarqube.gradle.SonarTask] Sensor Kotlin Sensor [kotlin]
2024-07-25T15:25:01.510+0200 [DEBUG] [org.sonarqube.gradle.SonarTask] The Kotlin analyzer is running in a context where unchanged files cannot be skipped.
2024-07-25T15:25:01.532+0200 [DEBUG] [org.sonarqube.gradle.SonarTask] Using Kotlin 1.9 to parse source code
2024-07-25T15:25:01.533+0200 [DEBUG] [org.sonarqube.gradle.SonarTask] Using the default amount of threads
...
260/260 source files have been analyzed
2 source files to be analyzed
2/2 source files have been analyzed

Here are all logs related to the importing. Other logs are pretty general. And also I found no error logs

[Colin]

It looks like the report is being read correctly.

@Nik2

/home/admin/workspace/project/build/reports/jacoco/test/jacocoTestReport.xml

Next I would suggest you actually open up this report to see if coverage is being reported as expected. SonarQube just reads the report, it’s not involved in generating the code coverage information.

[Nik2 (Nikita H)]

After the several researches it turned out that It was caused by broken ci. However searching the logs was a very helpful suggestion.
Thank you!