Code Coverage is showing 0.0% and Quality gates are not publishing as expected

[Revathi2823 (Revathi)]

1. Configured branches are showing in short-lived branches instead of long lived branches
2. Scanning works when run with PR branch and not working when run with main/master branch vice versa
3. Coverage showing as 0.0% showing No Conditions set on 9k lines of code
4. Security, Maintainability, Reliability, Duplications are showing some values but not code coverage
5. Would like to know what configurations need to be done to see some values in code coverage and for branching issues.

[Colin]

Hey there.

@Revathi2823

Configured branches are showing in short-lived branches instead of long lived branches

The docs should be helpful here.

As for coverage, what do the logs say about the import of coverage info?

How to find logs about importing code coverage

When coverage data isn’t appearing as expected in SonarQube Server / Community Build or SonarQube Cloud, 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 /…