Issue with sonar.branch.name in Azure DevOps Pipeline using SonarQube Community Edition v25.10.0.114

saichetan · October 15, 2025, 1:13pm

Hi Team,
I’m currently using SonarQube Community Build v25.10.0.114319, deployed as a pod in Kubernetes. I’m trying to integrate SonarQube scanning into my Azure DevOps pipeline, targeting a repository with the release branch set as default.
When the pipeline is triggered, I encounter the following error during the SonarQube Prepare Analysis task:
##[error]12:59:18.742 ERROR Validation of project failed:
o To use the property “sonar.branch.name” and analyze branches, Developer Edition or above is required. See Analysis parameters | Sonar Documentation for more information.
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘ClassRealm{iac}-org.sonar.iac.helm.HelmEvaluator’: Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name ‘AnalysisTempFolder’ defined in org.sonar.scanner.analysis.AnalysisTempFolderProvider: Unsatisfied dependency expressed through method ‘provide’ parameter 0: Error creating bean with name ‘DefaultInputProject’ defined in org.sonar.scanner.scan.InputProjectProvider: Failed to instantiate [org.sonar.api.batch.fs.internal.DefaultInputProject]: Factory method ‘provide’ threw exception with message: Validation of project failed:

I also noticed that:

Sometimes the scan works for one repository.
But from the second repository onward, the same error appears.
I tried explicitly setting sonar.branch.name= in the prepare task, but the error still persists.

Could someone please help clarify:

Is there a workaround for scanning non-default branches in the Community Edition?
Why does the error appear inconsistently across repositories?

Thanks in advance for your support!

Colin · October 16, 2025, 2:55pm

Hey there.

Here’s all the code for determining if the analysis is on a default branch or not.

github.com/SonarSource/sonar-scanner-azdo

src/common/latest/prepare-task.ts

b55ee411d


      
                tl.getVariable("Build.SourceBranch") as string,
              );
            }
          }
          
          /**
           * In the case of branch analysis, we need to know if we are on the default branch.
           * If that is the case, we try to not specify the sonar.branch.name parameter to avoid getting
           * rejected by SonarQube Server tiers that do not support it.
           */
          async function isDefaultBranch() {
            const collectionUrl = tl.getVariable("System.TeamFoundationCollectionUri") as string;
            const provider = tl.getVariable("Build.Repository.Provider") as AzureProvider;
            const currentBranch = tl.getVariable("Build.SourceBranch");
          
            if (provider === AzureProvider.TfsGit) {
              return currentBranch === (await getDefaultBranch(collectionUrl));
            }
          
            if (provider === AzureProvider.Svn) {
              return currentBranch === "trunk";

Do you see any messages in your pipeline like: Unable to get default branch, defaulting to 'master'?

Baskar_D · October 17, 2025, 8:06am

we also got that error in sonarqubeprepare@7 task

Unable to get default branch, defaulting to ‘master’

saichetan · October 17, 2025, 8:49am

Yes this is the error I am getting in sonar prepare task when using version 7. Is there any solution for this?

Topic		Replies	Views
Sonar.branch.name SonarQube Server / Community Build sonarqube , scanner , dotnet	3	4840	November 11, 2021
SonarQube doesn’t recognize branch name in version 10.6 when using Azure Pipelines SonarQube Server / Community Build sonarqube , azuredevops	4	507	July 3, 2024
Error: To use the property "sonar.branch.name" and analyze branches SonarQube Server / Community Build sonarqube , scanner , azuredevops-server	17	41179	July 24, 2020
Default branch not named master in Community Edition SonarQube Server / Community Build azuredevops-server	6	3316	November 29, 2019
Azure DevOps branch name issue with Default Branch SonarQube Server / Community Build sonarqube , azuredevops	20	4652	February 15, 2023

Issue with sonar.branch.name in Azure DevOps Pipeline using SonarQube Community Edition v25.10.0.114

Related topics