Help needed with MsBuild plugin

[David Aldrich]

Hi

 

I have used Jenkins for a long time but am now using the MSBuild plugin for the first time, because we are migrating some build jobs from VC2008 to VC2010.

 

I have added a ‘MSBuild installation’ in Jenkins with the following path:

 

C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe

 

In my job, I specify the following MSBuild command line arguments:

 

p:Configuration="My_release" /p:useenv=true /flp:logfile=MyOutput.log;verbosity=diagnostic

 

When I run the job I get this error:

 

error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified. 

 

Visual C++ 2010 is installed on the build machine and CL.exe is definitely present.

 

I guess that MSBuild would typically be executed from a Visual Studio command prompt which would have the environment variables correctly set up.

 

Do I need to configure the path when running the MSBuild plugin from Jenkins?

 

Best regards

 

David

 

[Dhrutib...@wellsfargo.com]

Hi,

 

Did you set up MSBuild configuration globally?

 

I mean, go to Manage Jenkinsà Configure System , you need to add which version of MSBuild you going to use.

 

Try above and let us know whether it solved your problem or not.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[David Aldrich]

Hi

 

Thanks for your reply.

 

Yes, I had already done that.

 

David

Click here to report this email as spam.

[Dhrutib...@wellsfargo.com]

Can you provide configuration settings for your job , if possible?

And what are the steps you are adding for MSBuild?

[David Aldrich]

I think there is not much to say.

 

The master configuration sets the MSBuild path to:

 

C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe

 

The build step is:

 

MS Build file: MSVC\MyProj.sln

Command line arguments: /p:Configuration=" release" /p:useenv=true /flp:logfile=MyOutput.log;verbosity=diagnostic

[Dhrutib...@wellsfargo.com]

Sorry David, but it is hard to understand your problem.

 

I am giving my code snippet so you can compare and check the difference.

 

Jenkins Job:

 

Execute windows batch command

                C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /t:Rebuild /p:Configuration=%BuildType% /p:Platform="%BuildPlatform%" /verbosity:normal  %workspace%MyProj.sln

 

 

And check whether you have set up environment variables on your build server. E.g. C:\winodws\system32

[David Aldrich]

Do you use the MSBuild plugin or just specify a ‘Windows batch command’ build step?

 

Does your path variable on your slave include:

 

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN;

 

?

[Dhrutib...@wellsfargo.com]

I set MSBuild.exe at configure system location and for my jobs , I just use the command ‘Execute Batch Command” and write my query.

It works for me so far.

[Mark Waite]

Isn't the message "error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified. " an indication that you may have failed to call vcvarsall.bat for your specific Visual Studio before starting the Jenkins slave agent on that machine?

I thought that Visual Studio used that technique to allow users to install multiple Visual Studio versions on a single machine, and then select which Visual Studio they want to use for a command line compile by invoking the corresponding vcvarsall.bat script for that Visual Studio version.

I don't think the MSBuild plugin is the right one to decide which Visual Studio version you want to run, though I guess it could be extended to have some form of list of alternative Visual Studio versions which it should attempt to configure before running the build.

Mark Waite

---

From: "Dhrutib...@wellsfargo.com" <Dhrutib...@wellsfargo.com>
To: jenkins...@googlegroups.com
Sent: Wednesday, September 4, 2013 9:42 AM

[David Aldrich]

Hi Mark

 

Thanks for your reply.

 

I have found this issue:

 

https://issues.jenkins-ci.org/browse/JENKINS-16452

 

where you have also discussed this.

 

Given that we run Jenkins as a Windows service, and given that it is not possible to run vcvarsall.bat in conjunction with the MSBuild plugin from Jenkins, I think it is best for us to use a ‘Windows batch command’ build step in the Jenkins job and call vcvarsall.bat and MSBuild.exe explicitly there.

 

It seems to me that the MSBuild plugin is not very useful because of this.

 

BR

David

[Ginga, Dick]

FWIW, We build for both VS 2008 and VS 2010. I have taken the contents of the vcvarsall.bat file and made it a Properties file on the master. Then I use “Prepare an environment for the run” and set the “Properties File Path” to $JENKINS_HOME\usercontent\vs2010env.properties and click “load script and properties file form the master” and the environment is all setup for using the MSBuild build step.

[David Aldrich]

Hi

 

Thanks for your suggestion. I’m not familiar with properties files but will have a look.

 

David

[William Soula]

When I had to create an msbuild job, a few years ago, I had to call vcvarsall.bat and then msbuild from within the same call otherwise the environment variables were lost because they were only set for that environment.  I had one batch command section with two lines, vcvarsall and msbuild and the msbuild call didn't have the environment variables set.  I had to figure out how to run two commands within the same dos call to keep them from being lost.

Possibly something like these:
http://www.autoitscript.com/forum/topic/54864-run-multiple-dos-commands-in-one-line/

Will

[David Aldrich]

Hi Dick

 

Do I need a particular plugin in order to use property files as you described?

 

David

 

From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Ginga, Dick

Sent: 05 September 2013 13:10

[Ginga, Dick]

Yup, Environment Injector Plugin

[Cyril Besse]

Hi,

Try in removing "/p:useenv=true" from MSBuild command line.
I had the same problem, and I lost 2 hours to understand

see link: http://msdn.developer-works.com/article/11302946/problem+with++useenv+in+visual+studio+2010+professional

Regard
Cyril