0
votes

We are upgrading our SonarQube server from 6.1 to the 6.7.1 LTS. We are running TFS 2017 on-prem. I have updated the plugins to: sonar-csharp - v 6.7.1.4347 sonar-css v 4.5 sonar-ldap - v 2.2.0.608 sonar-scm-git - v 1.3.0.869 sonar-scm-tfvc v 2.1.2 sonar-typescript - v 1.1.0.1079 sonar-web - v 2.5.0.476 sonar-xml v 1.4.3.1027

When running a build the complete analysis step fails Post-processing failed. Exit code :1

there are warning messages about sonar.cs.analyzer.projectOutPath property is missing.
And "No roslyn issues report not found for this project"

Also, it suggests that I re-run the scanner using the -X switch. but I haven't been able to find how to add that switch.

Any help on how to determine what/where the error is would be SUPER helpful.

2

2 Answers

0
votes

Have a look at this and this releasenotes. Check if you are using the latest scanner version: 4.0.2.892.

0
votes

In our case, the SonarQube API being called in the build step happened to start failing on special characters that it had not had trouble with before. We were using curly-braces in our sonarQube project names, and the newer version really did not like that. Once we changed the project names to use parenthesis instead of the curly-braces, things were working better