We are attempting to run sonar-scanner v22.214.171.1244 to parse our Gradle generated Jacoco coverage xml report. We have tried to upload our java coverage reports with sonar-scanner in two different ways:
sonar.jacoco.reportPaths– This worked for us and we see coverage results on Sonarqube, but required us to set the
sonar.test.binariesoptions to point to the appropriate Java build directories. Our only issue with using “reportPaths” is that it is deprecated, so we want to switch to using the
sonar.coverage.jacoco.xmlReportPaths– This does not work for us. We point it to the xml report path and we set all the same flags as the one above except for the
We were targeting pushing results to Sonarqube Developer Edition v7.3. To make sure it was not a bug with the webapp/deployment, we stood up another separate temporary deployment of Sonarqube Community Edition v7.9.2 LTS server, and attempted to push the results there with the same version of sonarqube scanner with the same two methods above; we still get 0.0% coverage with the
Is there a bug with scanner, or are we doing something wrong when invoking scanner?