Build-Wrapper, not starting MSBuild

Hello,

SonarQube version 7.9.1 Enterprise Edition
build-wrapper-win-x86-64.exe Version 6.6
sonar-scanner-cli

I run: build-wrapper-win-x86-64.exe --out-dir …\bw_output MSBuild.exe /t:rebuild /nr:false

I get an empty json dump file. I feel like its not running MSBuild.exe?
What should I do?

Snippet of build-wrapper.log:

Mon Feb 17 13:08:44 2020: build-wrapper, version 6.6 (win-x86-64)
Mon Feb 17 13:08:44 2020: isWow64: 0
Mon Feb 17 13:08:44 2020: windows version: 6.2, service pack: 0.0, build number: 9200, product type: 1
Mon Feb 17 13:08:44 2020: current directory: I removed it for this
Mon Feb 17 13:08:44 2020: command line received: <MSBuild.exe /t:rebuild /nr:false>
Mon Feb 17 13:08:52 2020: initializing json file
Mon Feb 17 13:08:52 2020: starting debug cycle
Mon Feb 17 13:08:52 2020: process created with pid: 15316
Mon Feb 17 13:08:52 2020: image path name: <C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe>
Mon Feb 17 13:08:52 2020: command line: <MSBuild.exe /t:rebuild /nr:false>
Mon Feb 17 13:08:52 2020: working directory: I removed it for this
Mon Feb 17 13:08:52 2020: isWow64: 1
Mon Feb 17 13:08:52 2020: skipping process C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe with pid: 15316
Mon Feb 17 13:08:52 2020: process created with pid: 16500
Mon Feb 17 13:08:52 2020: image path name: <C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe>
.
.
.
Mon Feb 17 13:08:53 2020: command line: <MSBuild.exe /t:rebuild /nr:false>
Mon Feb 17 13:08:53 2020: working directory: I removed it for this
Mon Feb 17 13:08:53 2020: isWow64: 1
Mon Feb 17 13:08:53 2020: skipping process C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe with pid: 21980
Mon Feb 17 13:08:53 2020: process with pid 23648 exit with code: 0 (0x0)
Mon Feb 17 13:08:53 2020: process with pid 13632 exit with code: 0 (0x0)
Mon Feb 17 13:08:53 2020: process with pid 20964 exit with code: 0 (0x0)
Mon Feb 17 13:08:53 2020: process with pid 21152 exit with code: 0 (0x0)
Mon Feb 17 13:08:53 2020: process with pid 15316 exit with code: 0 (0x0)
Mon Feb 17 13:08:53 2020: finalizing json file

Thank you

Hi @mitch,

what version of Windows are you using?

Would you be able to share the console log and the build-wrapper output dir?

Hi im using windows 10.
Console log just creates a new empty line and thats it. So it is empty.
the output dir is just the relative path: …\bw_output. I am storing it in the folder outside of the solution

Hi @mitch,

It is strange that console log is completely empty. From where are you launching the process? The dev visual studio prompt?

Hi @mpaladin
I am just launching it from a command prompt window. the same command works when I take the build-wrapper off of the prefix. But when I add the build-wrapper.exe it does not display anything.

Hi @mitch,

are you on Windows 10 32 bits?

Hi @mpaladin
I am on a 64 bit Windows 10 machine

Hi @mitch,

it is quite a strange issue you are facing, do you have some antivirus or protection which may interfere? Do you have a way to try on a different machine?

I’ve tried it on two other machines. Both company machines. When I run the build-wrapper with cl.exe on just a random .cpp file it will capture the output.

I compared the .log file to a working log file found online. It looks like my build-wrapper is capturing msbuild.exe create process and skip process over and over. While the working one only does that once, and proceeds to create different processes relating to the build.

Do you think this means there is a problem with the MSBuild?

Hi @mitch,

I am not sure what problem you are facing here, I’ve never seen it before.

Could it be that the /t:rebuild is not taken into consideration and it is actually not building anything?

Even if you are specifying /nr:false you could try to set environment variable MSBUILDDISABLENODEREUSE=1 which is supposed to have the same effect.

A post was split to a new topic: Empty build-wrapper-dump.json file