Hi, we’ve been using Sonar cloud analysis for a while now, it’s worked great, after the initial repo analysis it would only scan and report issues within files where we had new code.
However, a month ago or so, it started fully scanning the repo on every pipeline run, reporting all of the issues constantly and since we have some technical debt, this has made it unusable.
Our New code definition config is:
Number of days: 30
AzureDevOps
Project is dotnet c#
This is our PR pipeline config, which hasn’t been changed since we adopted SC a while back.
- task: JavaToolInstaller@0
inputs:
versionSpec: '17'
jdkArchitectureOption: 'x64'
jdkSourceOption: 'PreInstalled'
- task: SonarCloudPrepare@1
inputs:
SonarCloud: SonarCloud
organization: {redacted_organization}
scannerMode: MSBuild
projectKey: {redacted_project_key}
projectName: {redacted_project_name}
- task: SonarCloudAnalyze@1
inputs:
jdkversion: 'JAVA_HOME'
- task: SonarCloudPublish@1
inputs:
pollingTimeoutSec: '300'