These sample projects demonstrate some usage of Bazel with the bazel_sonarqube rules.
A typical analysis workflow in these examples will follow the steps:
bazel coverage //...bazel run //:sonarqube
Note that the analysis requires a connection to a SonarQube server.
If an external server is available, pass the arguments to the SonarScanner:
bazel run //:sonarqube -- -Dsonar.host.url=${SONAR_HOST_URL} -Dsonar.login=${SONAR_AUTH_TOKEN}
Alternatively, see https://docs.sonarqube.org/latest/setup/get-started-2-minutes/.
There is another example in //subproject-with-separate-sonarqube:sonarqube. This is to simulate a mono-repo where each subproject has its own sonarqube analysis target. This could be useful if you are only wanting to build/test/analyze a subset of the entire repo.
The usage pattern is similar to the single case except it limits the scope of the targets to the submodule.
bazel coverage //subproject-with-separate-sonarqube/...bazel run //subproject-with-separate-sonarqube:sonarqube