Thanks. The first thing I recommend checking then is that the SonarQube task (and the build definition that contains it) is only triggered on master branch. Community Edition does not support analysis of branches, so you need to make sure that SonarQube analysis only is performed on master (we’ve took a note here to make the documentation a little bit clearer in that aspect).

The current logic is that it looks at the Build.SourceBranch variable in TFS/VSTS environment (if you’re curious you can see the code logic here). For Git if it’s anything else then refs/heads/master then it will set sonar.branch.name, resulting in a failure if Community Edition is in use.

By the way before anything do make sure to run latest version of the SonarQube Extension : v4.3.2 as of writing.

After uninstalling cxx community pluging version 0.9.7 it looks my problems are solved! No CxxCoverageSensor problem and no sonar.branch problem with the first project i tried. Upgrading the SonarQube extension to version 4.3.2 was the solution. Thanks!

Community Edition only works on the default Master branch. Interestingly, I changed the default branch from master to develop and it SonarQube stopped working until I changed the default branch back to master.

Hello Guys, the only method to fix this issue is setting as default branch where you want generate a Build.(project settings-> code -> repositories --> branches -> right clic on the named branch -> set as default -> then run build pipeline).