we are using SQ 8.4.2 Developer Edition, we are using the sonar scanner during are c# compile.
Is it possible that the violations found during compile are not shown as Warning after compile. We want to enable the build option to treat warnings (brought by other places like by SQ rules) as Error?
I tried the silent option, but it only applies to the console output (as it is correctly described). Further research has brought me only to how to suppress a certain warning. But not if and how to not show all warnings caused by SQ in a build.
this example should clarify what we currently get displayed after the compile (c# no matter if dotnet or msbuild):
"blabla.sln" (Build target) (1) ->
"blabla\F1.csproj" (default target) (2) ->
blabla\F2.cs(60,15): warning S1135: Complete the task associated to this 'TODO' comment. [blabla\F1.csproj]
blabla\F3.cs(188,17): warning S1067: Reduce the number of conditional operators (5) used in the expression (maximum allowed 3). [blabla\F1.csproj]
blabla\F4.cs(351,17): warning S1067: Reduce the number of conditional operators (4) used in the expression (maximum allowed 3). [blabla\F1.csproj]
blabla\F5.cs(47,13): warning S3240: Use the '?:' operator here. [blabla\F1.csproj]
blabla\F5.cs(67,29): warning S107: Constructor has 8 parameters, which is greater than the 7 authorized. [blabla\F1.csproj]
5 Warning(s)
0 Error(s)
Is there a way to not display the detected issues as warnings in the compile (e.g. a general suppression)?