Project setup advice

SonarQube Cloud
1
  • ALM used: Azure DevOps
  • CI system used: Azure DevOps
  • Languages of the repository: Docker, C#, JavaScript/TypeScript, Python

Hi all, we have a new repository for a .NET Aspire project with integrated MkDocs which I’m a little unsure on the best way to approach this as far as the SonarQube project(s) are configured.

Our SonarQube instance is bound to our Azure DevOps organisation.

The options that I can see are:

  1. Create an unbound project per-technology per-component
  2. Create bound monorepo projects per-technology per-component

I’m assuming I cannot just use a single project in SonarQube for this setup, as the scanner would need configuring per language, and scan results cannot be combined?

Are there any other options/how would you approach this?

We’re not so worried about automatic scanning as we trigger scans on our “main” branches when there are merges to them.

Any advice greatly received. Many thanks

2

Hey @caosborn, you can actually have multiple languages in a project! It’s not 1 scanner per language: a scanner (in your case, Scanner for .NET) can analyze multiple languages. You just need to ensure all relevant source folders (API, front-end, Python bits, Dockerfiles, etc.) are visible to the scanner during the Scanner for .NET begin/analyze/end sequence. I recommend you have a look at the .NET multi-language analysis docs.

Of course, you can also set up a monorepo, but if your project doesn’t really follow a monorepo structure (with different subprojects having independent builds, CIs, PRs…) then I don’t recommend it, it would just make things complicated.

3

Great thanks @andres I’ll take a look. Sorry for the delayed reply.