Is this following branch issue known with Community edition : versions used (SonarQube Community Edition Version 7.3) error observed - Any branch(other than master) we select for CI from AzureDevOps(VSTS) for sonar analysis, it always shows project used master branch and not the specific branch us…

Sonar Community edition only identifies master branch

Vitreous (Vitreous) November 29, 2019, 12:19pm 9

Just came across an issue with this in Azure devops. Task *4 does not support multiple branches while *3 did

Topic		Replies	Views
Change default branch in SonarQube Community Version SonarQube Server / Community Build azuredevops-server	2	1910	December 17, 2019
Default branch not named master in Community Edition SonarQube Server / Community Build azuredevops-server	6	3297	November 29, 2019
Error: To use the property "sonar.branch.name" and analyze branches SonarQube Server / Community Build sonarqube , scanner , azuredevops-server	17	40899	July 24, 2020
Community Edition with VSTS: To use the property "sonar.branch.name", the branch plugin is required but not installed SonarQube Server / Community Build branches , azuredevops-services	17	17648	October 22, 2020
The master branch becomes the parent of our feature branches instead of the develop branch, resulting in too much "new code" SonarQube Cloud branches , azuredevops-services , github , pull-request , sonarqube-cloud	14	7235	October 23, 2019