I\'ve setup Static Code Analysis on my Visual Studio Team Services builds. I\'m using the \"MSBuild\" build step for my solution and in the build logs it shows 999+ lines that s
After some months of working with VSTS, my experience is as follows;
We've started using Build Quality Checks to fail the build when there are more warnings compared to the baseline.
Yes, just part of warnings in build display in the Issues section of build summary.
The workaround is that you can upload the code analysis result file (xml) through Logging Commands (##vso[task.uploadsummary]local file path
)and the content shall be added to build/release summary (Below Work items linked to associated changes section)
For example:
param(
[string]$p
)
Write-Host "##vso[task.uploadsummary]$p"
Arguments:
-p $(Build.SourcesDirectory)\WebAppAzureProfile\bin\WebAppAzureProfile.dll.CodeAnalysisLog.xml