Using Jenkins with LabVIEW for Continuous Integration


Continuous Integration (CI) is increasingly common among LabVIEW users and all software developers. For anyone not familiar, CI aims to automate the previously laborious task of building your software for distribution, either as a reuse library or a final product.

In case the benefits aren’t clear, automating this task is beneficial because:

  • It ensures it’s done early and often throughout development – many people otherwise wait until the end, only to discover new problems in the last mile
  • It can be used to automate regression and integration testing prior to build, which helps find bugs early and often
  • It offloads build processes from a development machine and can be used to parallelize several large build processes

One of the most popular and ubiquitous tools for this task is Jenkins, and I’m increasingly seeing a lot of our users employ a server that has Jenkins and LabVIEW for the sake of nightly build processes.

While many of you have figured this approach out on your own, I did want to share a tool from our Systems Engineering group that you can evaluate if you’re thinking about propping up your own Jenkins server.

This free tool provides a web service API that can be integrated with Jenkins for the sake of CI.

Enjoy:  LabVIEW CI Project

 

 

Advertisements
This entry was posted in Software Engineering Process, Tools. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s