Hi, I’m pulling my heair out with this issue. I’m getting ‘Could not find a default branch to fall back on.’. I’ve turned on debug mode and pasted the details below. Please help, It’s killing me. Nick ALM used - Azure DevOps CI system used - Azure DevOps Languages of the repository: Typescrip…

cliSources is actually sonar.sources, which is a list of paths where your sources are. sonar.tests contains paths where your test sources file are. Both can target the same directory, so then you’ll have also your test files analyzed by the scanners and raising issues if you need to. You can chec…

Hi @Nick_Raphael and welcome to the community ! Do you use the Azure DevOps extension for SonarCloud ? Mickaël

Thanks for the welcome. So, I started a new job and the first thing I have to do is hook our react applications Devops build up to sonarcloud. I’ve got npm running test and generating codecoverage report. But can’t seem to publish it up to the cloud. Our other backend dotnet builds are working f…

Can you please double check the organization name and the projectKey ? Most of the error that we had with this message came from a misconfiguration of those properties. Thanks

They seem fine. The .org name is correct for sure. But can’t I pick anything for the project key and it will create that project up on sonarcloud?

You need to create the project first on SonarCloud. So then you’re sure that the projectKey you set is not already used, so then after you can properly set it on Azure DevOps.

It can work for some cases, but this will be deprecated soon and dropped once we will have the binding between Azure DevOps and SonarCloud organization/projects. And also, are you analyzing the default branch of the repository at first ?

No, I’m analysing a branch off master. Does that change things?

Yep, If it’s a new project, then you need to analyze the default branch of the repo. I think that it needs to be master at first, then you can change in on SonarCloud to reflect your configuration if it’s not the case.

Holy crap, it worked!!! But I’m seeing this now… “master” branch has not been analyzed yet.

Help with following error... "Could not find a default branch to fall back on."

SonarQube Cloud

Nick_Raphael (Nick Raphael) June 3, 2020, 8:32am 8

Let me quickly try that. I was told that the project would be automatically created. Oh well.

Github action: Could not find a default branch to fall back on

Topic		Replies	Views
Could not find a default branch to fall back on SonarQube Cloud csharp , administration , github-actions , sonarqube-cloud	17	45073	January 18, 2024
Really confusing error (Could not find a default branch to fall back on): call for improvement SonarQube Cloud sonarqube-cloud	2	1443	April 6, 2021
Github action: Could not find a default branch to fall back on SonarQube Cloud sonarqube	6	1668	September 12, 2022
"Could not find a default branch to fall back on." error on PR SonarQube Cloud coverage , python , github-actions , sonarqube-cloud	4	933	January 30, 2024
Sonar-maven-plugin - Could not find a default branch to fall back on SonarQube Cloud maven , sonarqube-cloud	12	11149	May 11, 2020

Help with following error... "Could not find a default branch to fall back on."

Related topics