Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat NO coverage Information as 0% coverage #57

Open
MounikaKota9 opened this issue Apr 13, 2023 · 0 comments
Open

Treat NO coverage Information as 0% coverage #57

MounikaKota9 opened this issue Apr 13, 2023 · 0 comments

Comments

@MounikaKota9
Copy link

Currently if no coverage report is provided then no Metric is being generated. This is making quality gate pass as there is no metric available for SonarQube Quality Gate to read.

In order to Improve this, No coverage information should be treated as "0%" so that Quality Gates can define conditions even on projects without coverage analysis.

SonarQube Support Response: Custom plugins that are developed to work with SonarQube need to implement their own logic to force them to report coverage as a metric, even if the coverage is not configured. The Quality Gates will only take into account metrics that are reported to it. So, the burden is on the maintainers of custom 3rd-party plugins to implement this.

This is an example of how another plugin has handled the issue: Treat no mutation analysis information as zero (0) coverage · Issue #13 · devcon5io/mutation-analysis-plugin. Please reach out to the maintainer of the mule-sonarqube-plugin and ask them to update their plugin to add this functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant