We are using Enterprise 9.9 together with Team City and the Scanner plugin. I can currently only use version 4.8 of the scanner.
Scanning our large .net framework application (120 projects) can take 20 + minutes, even with a minimal quality profile (I just selected blocker rules, and deactivated all js and typescript rules). This would make our PR build take over 40 minutes.
Ive also tried building a single project. I dont think I can use the dotnet tool version of the scanner.
It seems like nearly all of the time is spent here:
And why can you only use the 4.8 version? For the SonarScanner for .NET, v4.8 is incredibly old (Nov. 2019). It’s version 5.9 of the scanner (note that the current version is 6.1) that adds support for fast PR analysis. So the fact that your PRs are currently slow - even with SonarQube 9.9, which supports fast PR analysis - is not surprising.
Thats good to know - if it’s doing a full full analysis of 120 projects… that could take a while.
There seems to be many ways to run the scanner in our company. The project Im on is about 15 years old so Im just working with the original build scripts and our Team City installation only seems to work on this version. There is a v 6 listed but it wont work. Some java version error.
Ive got a couple more things to try but I’ll see if I can get the TC team to update the agents.
Hi. I tried a different method to run the scanner v 5.5 and it’s still taking around 20 minutes. It the cli version.
I have limited access to the team city platform so I dont have any choice currently - unless I redo the whole build pipeline using a container. Im happy to do this but Im not convinced it will be any better.
Has the underlying branch been analyzed? If PR analysis doesn’t have access to a good cache from the underlying branch, then it’ll still have to do a full analysis.
Id say that will be the issue. Im not sure where the cache could be stored - we would need to persist it off the build agent I assume since the agents are randomly assigned to tasks. I’ll do some research.
So I now have a successful build and analysis of our master branch and pull request branches. Its still very slow though. For the New Code settings I have master set to Previous Version and Project reference branch set to master. Is that correct?
This one is unrelated, but you may want to follow up on it later
This is about SCM information. It looks like analysis didn’t have all the SCM data it needed to correctly identify what’s in the PR. You should find more evidence of that in your analysis log, if you look.
Without that data - without being able to identify what changed in the PR - we’re still back at analyzing everything.
|[21:05:10] :| [Step 6/6] 08:05:10.459 INFO: Sensor PHP sensor [php]
|[21:05:10] :| [Step 6/6] 08:05:10.461 WARN: The sonar.modules is a deprecated property and should not be used anymore, it inhibits an optimized analysis
|[21:05:10] :| [Step 6/6] 08:05:10.474 INFO: Starting PHP symbol indexer
We dont use PHP and I excluded any rules for the language in the profile.
Im not sure where this is coming from. There’s nothing in our pipeline parameters for it. Maybe it’s not relevant?
If you want to upgrade to 10.4 (10.4.1 due today, so wait til that’s out) then you’ll be able to enable a mechanism to download (and run) only the language analyzers relevant for the current project. Note the caveat.
I should have mentioned that this feature will only save a few minutes at best. If you check the timing on the irrelevant sensor invocations, you’ll see they’re sub-second.
