Sonar Community edition only identifies master branch

souvikm15 · November 13, 2018, 8:48am

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 used during build.

julienlancelot · November 13, 2018, 9:39am

I’ve moved this thread to Get help -> SonarQube as this is not a bug.

julienlancelot · November 13, 2018, 9:41am

The analysis of branches and pull requests is available in the Developer Edition. See https://www.sonarsource.com/plans-and-pricing/developer for more details.

Regards

souvikm15 · November 13, 2018, 9:48am

Thanks Julien, so Community edition will ONLY help analyse master branch and not any other DEFAULT branch like develop or any custom branches. As per our expectation(see the code below) Community edition should work against default branch.

github.com

SonarSource/sonar-scanner-vsts/blob/master/common/ts/prepare-task.ts#L87


    props['sonar.pullrequest.provider'] = 'github';
    props['sonar.pullrequest.github.repository'] = tl.getVariable(REPO_NAME_VAR);
  } else {
    tl.warning(`Unsupported PR provider '${provider}'`);
    props['sonar.scanner.skip'] = 'true';
  }
} else {
  let isDefaultBranch = true;
  const currentBranch = tl.getVariable('Build.SourceBranch');
  if (provider === 'TfsGit') {
    isDefaultBranch = currentBranch === (await getDefaultBranch(collectionUrl));
  } else if (provider === 'Git' || provider === 'GitHub') {
    // TODO for GitHub we should get the default branch configured on the repo
    isDefaultBranch = currentBranch === 'refs/heads/master';
  } else if (provider === 'Bitbucket') {
    // TODO for Bitbucket Cloud we should get the main branch configured on the repo
    // https://github.com/Microsoft/vsts-tasks/issues/7595
    isDefaultBranch = currentBranch === 'master';
  } else if (provider === 'Svn') {
    isDefaultBranch = currentBranch === 'trunk';
  }

ganncamp · November 14, 2018, 7:59pm

Hi,

To be clear, Community Edition is always going to analyze whatever code you give it as master, regardless of the branch named used in your SCM. To be explicit, this is working as designed.

Ann

Mat_DeLong · August 2, 2019, 3:33pm

Was SonarQube changed ‘recently’ to not support multiple branches in the free edition?

ganncamp · August 2, 2019, 5:46pm

Hi @Mat_DeLong,

SonarQube used to offer a sonar.branch analysis parameter which took the provided value and hacked the analyzed project’s key to be mainProjectKey:valueOfBranchParam with the effect of analyzing the branch as an entirely separate project. That parameter was indeed removed “recently” - in 7.8. As you might guess, you can replicate the effect by just passing in a different project key.

That’s the only “branch analysis” that Community Edition ever had.

Ann

ganncamp · September 5, 2019, 11:08am

5 posts were split to a new topic: Default branch not named master in Community Edition

Vitreous · November 29, 2019, 12:19pm

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