-
Story
-
Resolution: Done
-
Normal
-
None
-
All / Cross Project
Extend global-jjb C/cpp/cxx Sonar analysis implemented in jjb/lf-c-cpp.jobs.yaml and shell/cmake-sonar.sh to accept specification of (a) file(s) with code-coverage data.
This is done by specifying a property for the sonar scanner. The relevant properties (with their wildly divergent use of report*s* and Path*s*) are documented here: https://docs.sonarqube.org/latest/analysis/coverage/
sonar.cfamily.gcov.reportsPath
sonar.cfamily.llvm-cov.reportPath
sonar.cfamily.vscoveragexml.reportsPath
sonar.cfamily.bullseye.reportPath
Very closely related:
The old gerrit-cmake-sonar job defined in lf-c-cpp-jobs.yaml installs sonar scanner via wget from Sonar then runs it.
The new generic gerrit-sonar job defined in lf-ci-jobs.yaml invokes a Jenkins SonarCloud plugin.
Is it time to upgrade the cmake sonar job to use the plugin, or is there some torturous complication that I just have not hit yet?
- is cloned by
-
RELENG-2767 Define python-sonarcloud template to eliminate mvn-settings and pom.xml
- Done