- Sonar: 10.1
- License: Enterprise licence
Our project
- C#, .NET 7
- 966.000 LOC
After sonar integration into Azure Devops our pipelines started to process longer without any very positive trend. We would expect some incremental scans.
Our azure implementation:
Before build:
steps:
#Prepare Analysis Configuration task
- task: SonarQubePrepare@5
inputs:
SonarQube: ‘SonarQubeProject’
scannerMode: ‘MSBuild’
projectKey: ‘xas-border_cihla_AYpfUTWWefsutADW31’
displayName: SonarQube Prepare Analysis Configuration
After build:
steps:
#Run Code Analysis task
- task: SonarQubeAnalyze@5
displayName: SonarQube Code Analysis
Situation day by day:
Prior sonar (also writing sonar parts of builds so that it is consistent)
1.9. (1st of September)
Sonar prepare: 0m
Backend build: 7m16s
Sonar analyze: 0m
With sonar
4.9. - FIRST SONAR RUN
Sonar prepare: 2s
Backend build: 25m46s
Sonar analyze: 5m49s
6.9.
Sonar prepare: 2s
Backend build: 22m4s
Sonar analyze: 5m3s
9.9.
Sonar removed
Sonar prepare: 0s
Backend build: 9m18s
Sonar analyze: 0s
So average time of build jumped from 8 minutes to 23 minutes and we additionally have to wait about 5 minutes because of Sonar analyze.
Is this normal or could there be any problem anywhere? We cannot have 30 mins more in build time.
Thanks,
Roman