Analyze projects vs manually create sonar cloud project

[nagarjuna183]

Hi team,

We are using Azure DevOps, and our code coverage tool is Sonar Cloud. Now we are planning to create project automation with the use of web API calls instead of manually setting up and importing projects.

1. What is the difference between web API calls to create projects and manual setup?
2. Which is good for practice, and why?
   
   

Thanks,
Nagarjuna

[Colin]

Hey there.

When creating a “manual” project, it will not be [bound] by default (Bind your DevOps platform & SonarCloud) and will therefore not support features like PR Decoration.

You can bind after the fact (that’s a new feature!) in the project administration, and reverse engineer the Web API to figure out how to do that in your automation.

[nagarjuna183]

Thanks Colin,

So, you mean If we choose to use an automation script, it will add the project but not provide PR decoration. Alternatively, we can use import projects and set up new code as clean policy? Is it correct?

Are there any web API calls available for automation to import projects and set up new code as clean policies?

Thanks,
Nagarjuna

[Colin]

Hey there.

@nagarjuna183

and set up new code as clean policies?

I don’t really understand what you mean by this.

[nagarjuna183]

above two options select with web API calls without manually selecting the options.

Thanks,
Nagarjuna

[Colin]

Take a look at the guide I sent you earlier.

How to reverse engineer the Sonar Web API

Every action that is taken in the SonarQube / SonarCloud UI is driven by the Web API. There is nothing you can do in SonarQube / SonarCloud that you cannot do using the Web API. We put a great deal of effort into the UI and UX of our products and sincerely think that most actions should be completed there. Especially when it comes to viewing analysis results, the UI is the best place to view up-to-date information with the right context. We think it is much better that you give access…