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.
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.