sonar.cfamily.build-wrapper-output.bypass is no longer supported on SonarCloud as it is using a new version of SonarCFamily (v6.0) where this long deprecated parameter has been dropped.
Thanks for your reply.
I’ve check this part of the doc and I tried to set a path instead of using bypass. But I had an error
java.lang.IllegalStateException: java.nio.file.NoSuchFileException: /Users/vagrant/git/./sonar-scanner-3.2.0.1227-macosx/bin/build-wrapper-dump.json
Indeed I don’t have a build-wrapper-dump.json but I don’t know how to download the Build Wrapper.
In the doc they told to download on local host has they create the server themself but I don’t know how to find the Build Wrapper in my case (I use SonarCloud).
I was not able to find mention of that in the doc.
I am having the same issue when running a build from a Build Definition in Azure DevOps on a private build server.
The following message is shown in during the ‘Run Code Analysis’ task:
ERROR: Error during SonarQube Scanner execution
ERROR: java.nio.file.NoSuchFileException: C:\A\1_work\87\bw_output\build-wrapper-dump.json
ERROR: Caused by: C:\A\1_work\87\bw_output\build-wrapper-dump.json
ERROR:
The SonarQube Scanner did not complete successfully
19:32:27.25 Post-processing failed. Exit code: 1
C:\A\1_work_tasks\SonarCloudPrepare_14d9cde6-c1da-4d55-aa01-2965cd301255\1.6.0\classic-sonar-scanner-msbuild\SonarScanner.MSBuild.exe failed with return code: 1
I have download the Build Wrapper and I have copied the files to the private build server and set a path to the folder where I have copied the files (build-wrapper-win-x86-32.exe and build-wrapper-win-x86-64.exe).
I have set the sonar.cfamily.build-wrapper-output to bw_output
The solution that is build contains C#, VB.NET, C++
Without C++ analysis everything is going fine, however I would like also to have analysis on the C+±code.
Do you have a suggestion what could be wrong or did I missed ?
Thank your for your reply. I have finally fixed this issue by replacing the build solution task through a command line script task which is calling the build-wrapper-win-x86-64.exe with the msbuild-command.
This is generating the build-wrapper-dump.json-file.
So I have missed a step