New project for dotnet repository in sonarcloud stuck on "This project has not been analyzed yet"

I’m using sonarcloud and after creating a project for a dotnet repository the ui is showing a “Project is not analyzed yet.Configure analysis” message. Following the link, however, leads to the project page with only a “This project has not been analyzed yet.” and seemingly no way to action it.

What am I missing here to unblock the initial automatic analysis of the project?

Hey there.

It sounds like your user is missing the Execute Analysis permissions on the project. A project administrator can add that, and you may want to adjust the default permission template if you expect to have this permission on all new projects.

Hi Colin,

Thank you for the reply. Unfortunately, that does not solve the issue.

  1. The user (me) has Admin permissions
  2. I was able to add a different repository, a front end a java script one, and the project there worked as expected with automatic analysis working immediately.

As a debugging step: Since posting this I was also able to run a scan locally using SonarScanner.MSBuild.exe with set to . That succeeded. Automatic analysis, however, remains broken with no indication whatsoever as to why. This means my team is not able to take advantage of clean as you code since there is no analysis for each PR.

Thanks. I was going off of your error message – you’re sure that this user has Execute Analysis permissions on this specific project?

What happens when you try to enable it under project-level Administration > Analysis Method? Does it tell you that it failed, for some reason?

I for sure have Execute Analysis permission. It turns out, however, I did not have “Administer Organization” permissions (despite being an Admin). This prevented me from seeing most of the additional settings under the project “Administration” flyout. Once I gave myself that permission using my admin permissions I was able to see the error trace ID:

Last analysis failed Analysis ID “eb25f31d-0757-41bb-b8c4-b22aef6add76”

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum and provide the following failing analysis ID: “eb25f31d-0757-41bb-b8c4-b22aef6add76”.

Thanks. With that ID, I’ll hand it along to the right team.

Hey @denisrevduplo

Welcome to the Sonar Community!

I checked the logs for the Analysis ID you shared. I can see the following error:

File xxx/xxx/xxx/xxx/xxx/appveyor.yml can't be indexed twice. Please check that inclusion/exclusion patterns produce disjoint sets for main and test files

If you have a configuration file in your repo, please check the inclusion/exclusion patterns as per the documentation here

Another possible reason for this is that you changed these values in the UI through Your Organization > Your Project > Administration > General Settings


1 Like