Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Automating the build of MSI setup packages on Jenkins

DZone's Guide to

Automating the build of MSI setup packages on Jenkins

· DevOps Zone ·
Free Resource

Don’t let inefficiencies in software testing lead to delayed deployments and poor quality products. Get the 90 Days to Better QA Guide by Rainforest QA for best practices to avoid these common pitfalls.

A short "how-to" based on an issue one of my work mates recently faced when trying to automate the creation of an MSI package on Jenkins.

Normally, Visual Studio solutions can be build on Jenkins by using the appropriate MSBuild plugin. Apparently though, for Visual Studio setup projects, MSBuild cannot be used and one has to switch to using Visual Studio itself to execute the build.

So the first approach was to use devenv.exe as follows

devenv.exe VisualStudioSolution.sln /build "Release"

While this works, the problem is that it is an "async call", meaning that the compilation goes on in the background while the console from which the build is executed, immediately returns. Obviously this isn't suited for being used on Jenkins. Searching around for a while, it turned out that you have to use devenv.com instead of devenv.exe:

"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.com"VisualStudioSolution.sln /build "Release"

Once you got that, integrating everything into Jenkins is quite straightforward:

(Obviously you may also simply set an environment variable pointing to devenv.com on your build server rather than indicating the entire path)

Discover how to optimize your DevOps workflows with our on-demand QA solution, brought to you in partnership with Rainforest QA.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}