We have a mono repo with many different projects within it. We’re using Azure DevOps with self-hosted build agents to build this. Most of the projects are C# .Net projects.
I’ve wrapped the build and test steps for the projects in “SonarCloudPrepare” and “SonarCloudAnalyze” steps. For the most part this seems to work well with each project getting its own analysis.
My question is though that there are a few projects/solutions within the monorepo that we do not want to run sonar over. Even though they are not surrounded by the Sonar steps it appears that when they are build they are running longer than before Sonar was introduced. I looked into the logs and i can see when they build that sonar is running on those projects too, even though they shouldnt be.
I see things like:
throught the logs of the projects NOT wrapped with SonarCloudPrepare and SonarCloudAnalyze steps.
Why is Sonar running over these when it shouldnt be? How can I stop it?
Another potential scenario we have is that sometimes i might want to run a build with sonar, then a build without it (using a build flag). Our self hosted agent during the day will often run incremental builds (i.e. it doesnt clear everything to save time), this also appears to be slowed by the fact sonar is running even though its not been requested to.