Evaluation help

SonarQube Cloud
1

Hi all.
I’m new to SonarCube. I’m running an evaluation and there’s a few things I’m trying to work out before we make a decision on what to do.

We’re running on Azure DevOps, with their own git repos. I’ve got my PR/CI builds happening within DevOps too.

I have an a couple of repos I’m doing testing with. A really small repo with a console app, written in vb.net, and a SQL server database. There’s around 1.7 lines of code in there. I’ve managed to create a baseline against this.

The 2nd repo is big, it’s got around 1.2m lines of code. Several c# webforms apps. Several console apps, a few desktop apps, and quite a few SQL server database projects too.

Regarding the 2nd repo - is it best practice to break things up in to individual repos for sonarcube to run analysis against? I can’t see any real benefit in keeping it as one super repo tbh.

2

Hi,

Welcome to the community!

Regarding your second repo, standard practice is to analyze the whole build. So if everything in the 2nd repo builds together, then it would make sense to have it as one SonarQube project. The only time we advise breaking from that practice is when the project is just too big to practically analyze all at once (i.e. very, very rarely.) Even at 1.2m LOC, you should be good, although be aware that adding analysis will slow down your build.

 
HTH,
Ann