DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Triggering Jenkins Build Remotely Using API
  • Multi-Agent Software Engineering: Can AI Teams Build Production Systems?
  • Arm64 Is No Longer the Edge Case
  • Build Your First Knowledge Graph From Unstructured Documents Using Python

Trending

  • How Performance Engineers Find and Fix Hidden System Bottlenecks
  • Prevent Duplicate API Calls With Idempotency: Patterns That Work
  • Pragmatic Premature Optimization
  • The Bottleneck of Scaling
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. Automating the build of MSI setup packages on Jenkins

Automating the build of MSI setup packages on Jenkins

By 
Juri Strumpflohner user avatar
Juri Strumpflohner
·
Mar. 13, 14 · Interview
Likes (0)
Comment
Save
Tweet
Share
13.7K Views

Join the DZone community and get the full member experience.

Join For Free

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)

Build (game engine) Jenkins (software)

Published at DZone with permission of Juri Strumpflohner. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Triggering Jenkins Build Remotely Using API
  • Multi-Agent Software Engineering: Can AI Teams Build Production Systems?
  • Arm64 Is No Longer the Edge Case
  • Build Your First Knowledge Graph From Unstructured Documents Using Python

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook