Hi,

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

Regard
Cyril

Le mercredi 4 septembre 2013 13:28:10 UTC+2, David Aldrich a écrit :
>
>  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
>
>  
>  

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f1a22d3a-4c7a-4fde-9055-7b86beb03b64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to