Hi there, thanks for the useful information in this discussion!
I’m experiencing the exact same problem, while we are using the ‘Developer’ edition (currently on a trial license).
When using mercurial as the scm, the default branch is called ‘default’ (as opposed to ‘master’ for git). We have Jenkins CI set up to create the projects (which works fine), but it will create it as ‘master’ in SonarQube. After the first run, we can manually modify this on the project level.
This seems to fully correspond with the analysis by @OlivierK;
The problem is that you must have at least one branch analyzed to define the default/main branch. You cannot do it before that branch has been analyzed.
and therefore I’m also interested in the following comment;
This creates by default in SonarQube a branch named master . It’s probably not an excellent idea to always call the main branch master by default, we may fix that in the future.
Notifying @Nathan_Chase, as we had contact about this via email.