- We are using SonarQube Developer Edition Version 9.9.1 (build 69595)
- SonarQube is deployed as a container in EKS
- The quality gate result is not consistent. Using the same commit (a rerun of the same pipeline job) the quality gate failed and passed.
- Tried using this option to verify the quality gate result, but the behavior is still the same
It looks like on one commit, coverage information is being provided (and a value of 83.7 is calculated), and on another commit there is no coverage information being passed (the value is 0).
Is code coverage being produced in each build preceding the analysis?
For example, two separate developers could have the code checked out – one who is running
mvn clean package sonar:sonar -DskipTests=false and one who isn’t skipping tests. This is one of many possible explanations for a discrepancy like this.
Colin, Thanks for responding.
This is not a manual run. We have a harness pipeline and mvn sonar:sonar is executed in an ephemeral container. So, every pipeline run has no data from previous pipeline execution.
going to verify coverage report on a failed run, this may provide more details on the root cause.