Visual Studio Environment

31 views
Skip to first unread message

msm...@autologue.com

unread,
Apr 26, 2018, 10:40:21 AM4/26/18
to Jenkins Users
Hey All, 

Just a sanity check.  I am getting familiar with Jenkins and using the msbuild plugin for Visual Studio solutions/projects. With regard to generating a package to a filesystem for deployment; I have found that the msbuild  only works if I set up the environment using the Visual Studio Developer startup script.  I must be missing something as I've seen numerous examples of msbuild generating a package for Web Deploy without mention of such a step?  Is using the script to set the environment for a Visual Studio solution a common practice? Hope that made sense

Mark Waite

unread,
Apr 26, 2018, 4:17:52 PM4/26/18
to jenkins...@googlegroups.com
That was my experience as well.  It has been a long time since I worked with Visual Studio based build projects, but all the projects I did seemed to require a prior call to the environment setting script.

Mark Waite

On Thu, Apr 26, 2018 at 8:40 AM <msm...@autologue.com> wrote:
Hey All, 

Just a sanity check.  I am getting familiar with Jenkins and using the msbuild plugin for Visual Studio solutions/projects. With regard to generating a package to a filesystem for deployment; I have found that the msbuild  only works if I set up the environment using the Visual Studio Developer startup script.  I must be missing something as I've seen numerous examples of msbuild generating a package for Web Deploy without mention of such a step?  Is using the script to set the environment for a Visual Studio solution a common practice? Hope that made sense

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1a8c10ba-4f82-470f-b02f-144e85845af6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

David Aldrich

unread,
Apr 27, 2018, 6:44:45 AM4/27/18
to jenkins...@googlegroups.com

We build Visual Studio C++ projects using Jenkins. We don’t use the MSBuild plugin but simply call msbuild from a bat step.  It is necessary to call the Visual Studio Developer startup script first, from within that step.

 


For more options, visit https://groups.google.com/d/optout.

Click here to report this email as spam.

Michael Small

unread,
Apr 27, 2018, 10:08:47 AM4/27/18
to jenkins...@googlegroups.com
Dave!   

We are using Visual Studio 2017; if possible, may I ask you to provide the actual statements in the build step bat script?  The MSBuild plugin actually builds the solution without issue, however the package deploy switches do not work properly if at all, and of course works perfectly from the VS Developer's prompt. Also any insight with regard to the Jenkins local system account permissions/account attributes would be very helpful. We are running Jenkins as a service and I am starting to suspect there may be a few "gotcha's" in the Windows environment as well. 

Thank you so much, 

On Fri, Apr 27, 2018 at 3:44 AM, David Aldrich <David....@emea.nec.com> wrote:

We build Visual Studio C++ projects using Jenkins. We don’t use the MSBuild plugin but simply call msbuild from a bat step.  It is necessary to call the Visual Studio Developer startup script first, from within that step.

 

From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: 26 April 2018 21:17
To: jenkinsci-users@googlegroups.com
Subject: Re: Visual Studio Environment

 

That was my experience as well.  It has been a long time since I worked with Visual Studio based build projects, but all the projects I did seemed to require a prior call to the environment setting script.

 

Mark Waite

 

On Thu, Apr 26, 2018 at 8:40 AM <msm...@autologue.com> wrote:

Hey All, 

 

Just a sanity check.  I am getting familiar with Jenkins and using the msbuild plugin for Visual Studio solutions/projects. With regard to generating a package to a filesystem for deployment; I have found that the msbuild  only works if I set up the environment using the Visual Studio Developer startup script.  I must be missing something as I've seen numerous examples of msbuild generating a package for Web Deploy without mention of such a step?  Is using the script to set the environment for a Visual Studio solution a common practice? Hope that made sense

--
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-users+unsubscribe@googlegroups.com.

--
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-users+unsubscribe@googlegroups.com.

Click here to report this email as spam.

--
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-users+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bc448bc4e2a64cfa9e62c95c0eae2a8f%40EUX13SRV1.EU.NEC.COM.
Reply all
Reply to author
Forward
0 new messages