Sonarqube version: sonarqube10.5
SCM: Gitlab-Ultimate
CI Tool: Gitlab-CI(.gitlab-ci.yml)
Hi team,
I have an parent project in Gitlab with many child projects. Now, this is integrated with Sonarqube. So, whenever I have to import any project, I just go to Create project —> From Gitlab —> selct my project from list
Now, earlier it was working fine but from last two days when I am trying to import my project it directly gives me the message ‘“master” branch has not been analyzed yet.’ The screen just strucks at this and there is no options shown.
Earlier when I used to import project it used to ask me to create a sonar token and then provided the code to add in gitlab-ci for sonar scanning. But, currently it does not give me these options. Any idea on how to fix this? is there some kind of limitation on OpenSource SonarQube?
Note: I first tried to import this project from my user locally and I tried running CI pipeline. It gave me error. So, I deleted the project and tried importing it from admin user credentials. Now, it started giving ‘branch has not been analyzed yet.’ issue.
Welcome to the community and thanks for this report!
You say the behavior changed in the last two days. What else changed in those two days? I ask because there aren’t any limits on the SonarQube side that would change this behavior.
Since what you’re observing is a UI change, it might also be worth checking your browser console log to see if anything interesting shows up there.
Thanks for reaching out. I tried checking the browser console logs as you mentioned but could no find any useful info. Also, as mentioned the issue remains the same. Whenever, I am importing any new project, it just gives me this screen as shown in the screenshot below:
I am only able to see the message: “env-develop” branch has been not analyzed yet
Here ‘env-develop’ is my default branch. There is nothing else I can see on the screen. My Sonarqube project just keeps stuck here. Earlier, whenever I used to import new project it used to ask me to create project token followed by the step to add properties in pom.xml file. But, this behaviour has changes as I mentioned and I am not getting these steps.
No, we didn’t do any sort of version upgrade. Our SonarQube version is same from the beginning(10.5). Apart from this, I also confimed with my team. We have not made any changes. Is there a way to check if someone made any sort of change which is resulting in such discrepancy.
There is one thing that I would like to mention. I first tried importing this project using my user credentials. But, then I deleted the project as it was giving me some error. Post, that I tried importing it using admin creds and it started me giving me ‘branch not analyzed’ message.
Can you try re-importing it with a different project key? You can re-key it later if you like.
If you drill into your existing project you’ll likely find that a non-main branch or PR has been analyzed, which is why the project switched over from the onboarding UI to the “main branch is empty” message.
