windows - Msbuild works via VS and command-line, but fails via Jenkins -
windows - Msbuild works via VS and command-line, but fails via Jenkins -
i trying build vs .sln has multiple c++ .vcproj's in it. solution file generated using cmake , i've got part working in jenkins (with cmake builder plugin). build solution file, using msbuild. able build solution using both visual studio , command line next command:
c:\jenkins\workspace\soniotest>"c:\windows\microsoft.net\framework\v4.0.30319\msbuild.exe" /t:rebuild bin/sonio.sln
this builds (on same machine jenkins resides).
however, trying automate portion of build in jenkins , build ends failing couple of c1083
errors ("cannot open source file: '..\path\to\file.ext': no such file or directory
). have tried using both jenkins msbuild plugin , using exact same command works in terminal "execute windows batch command" build step, same result.
when using windows batch command build step, can see in log command beingness executed:
c:\jenkins\workspace\soniotest>"c:\windows\microsoft.net\framework\v4.0.30319 msbuild.exe" /t:rebuild bin/sonio.sln
... same 1 works command line, including working directory.
i running jenkins service , have service logon business relationship (with administrator privileges). know directory jenkins execute batch commands out of?
any ideas why i'm seeing difference of behavior between jenkins , command line?
this much workaround solution, ended using devenv
instead of msbuild
, works fine.
i know hints beingness environmental issue, since it's not problem have vs installed on build server, decided save time spent in msbuild rabbit hole.
windows msbuild jenkins
Comments
Post a Comment