Template for a good new topic, formatted with Markdown:
ALM used : Azure DevOps
CI system used : Azure DevOps
Languages of the repository: C#
Error observed: Extremely slow build times
We are trialing Sonar Cloud, and our build times have gone from 10 minutes, so not finishing after 2 hours.
I have tried disabling warning that appeared the most (Using clause which was unusued), but this doesn’t seem to have an impact.
All the threads on here about it reference bugs that look to be fixed.
I don’t really know where to start debugging or getting support. Is this expected behaviour? ITs about 150 cs projects, none of them very big.
Could you clarify a little bit?
Are you saying that you build 150 projects C# and it went from 10 minutes to more than 120 minutes?
Does this mean you run SonarCloud analysis on each project?
If t’s the case and we consider the following:
the SonarCloud scanner scans every project = 150 analysis to perform
each analysis takes 1 minute to scan the code which is quite fast (but can be improved if the scope is reduced to the minimum) = 150 minutes of code analysis. Even with a 30 seconds step, the build time will be multiplied by 8.
At this scale, 150 projects, every new step which does something signififcant (and the scanner does look for a lot of things) will obviouly make the whole process longer.
Hi Olivier,
A background task example is AXU0Gk3BKGBZPjxNtwmS
In our situation (where we have a big monolith), and the time is as expected - how often would you run analysis then? We wanted to run it on every Pull Request, so that we could see any warnings in the PR review stage - which I understand we can do. But with it adding 3 hours on, its just not feasible everytime.
We could run it once a week to review I guess…
Are there certain checks we can turn off to get the time taken right down?
Sorry I have been on holiday, still on list - hopefully by end of week.
Also to confirm I did send build log to your colleague. We were just going to test the one project that is really slow, and see if I can send through to you.
Hi @tank104 - please let us know if there’s any help you need in the investigation and if you want to continue the discussion in a private thread, to share logs and code more freely.
An update: @tank104 sent us a reproducer via a private thread and we identified the problem and added a comment to an existing issue we’ve had in the same area. We now have more information to tackle the problem, for which we are grateful.