Peter van Zetten

Hi @cjohnstoniv, I assume this is caused by a difference in the OSX sed version. I'm afraid I haven't got access to a Mac to test it, but I'm happy...

Thanks for the change! I like the sound of this - I've got a project which will soon need to get JS/TS tests and coverage tracked in SQ. I don't...

@amdonov Thanks for the report. Which bazel-sonarqube commit are you running with? And what's your build environment - particularly are you using a remote cache or buildfarm/buildbarn? Commit 4f62b4c fixed...

@amdonov Ok, I've made a couple of fixes for Bazel 2.1.0 compatibility - I don't think this was affecting you, but maybe. I've also fixed the None check for coverage_report,...

To capture the Bazel 2.1.0 compatibility issue the dependencies are now mandatory - `bazel_skylib` and a version visibility hack. Do you have in your WORKSPACE: ``` load("@bazel_sonarqube//:repositories.bzl", "bazel_sonarqube_repositories") bazel_sonarqube_repositories() ```...

I'm afraid I haven't done _any_ testing with golang projects. That said, I would hope that if bazel's own coverage report is correct, the SQ format conversion will be fine....

Hi @amdonov, @prashilgupta, in a recent commit I updated the coverage collector to copy the latest changes from the upstream lcov coverage aggregator. Maybe this has had some effect on...

Hi @fcandalija! Using archives as inputs to the `sonar.java.binaries` property seems to work with the standard Java analyzer (or it would fail for me too!), but it looks like the...

In my own project the NodeJS/TS tools are installed in the build environment, and to be honest my JS colleagues aren't really interested in the SQ side of things, so...

Maybe I've misunderstood, but could this be managed already by creating individual `sonarqube` targets instead of `sq_project` targets collected into a single `sonarqube`? You'd have to analyse each one individually...