Thanks to everyone who attended my technical session at NIWeek 2012, "Fire and Forget: Bulletproof Builds Using Continuous Integration With LabVIEW." The session was at the end of the last day of the conference, but the attendance and the energy was still great!
Continuous Integration (CI)–continuously building and integrating your application to reduce risk and improve quality–is an important part of modern professional software development. There are many ways to implement CI for your LabVIEW projects, and in this presentation I describe how JKI has integrated Jenkins into our build process and how you can do the same thing in your organization.
But first, I'd like to present to you 'the missing slide' from my presentation. I omitted an overview of what the CI process looks like from high above.
Of course, things can get more interesting as you automate more and more of your build and release (i.e. integration) processes - as I show in my presentation and in the sample code below. In the presentation example, we're continuously building a VI Package using VIPM's new API - but you can easily imagine doing the same thing for a LabVIEW built executable or installer.
If you want to get a jump-start on using Jenkins with LabVIEW in your organization, download the sample code from this presentation and get started.
If you're interested in Continuous Integration support services from JKI, contact us and we can discuss your CI needs and whether JKI services could help!
How do you bulletproof your LabVIEW builds? Join the conversation in the comments.