Bug fixes

Fixed bug where an error would be thrown if VIPM was not running when script attempted to kill the process.
Added step and script to set next VI Package build number based on the highest of: build number in vipb file, build number of Jenkins job, build number deployed to a VI Package Repository.

Build system using LabVIEW-CLI

Groovy scripts and LabVIEW Package of build steps to support continuous integration using tools such as Jenkins.

You'll need:
https://github.com/JamesMc86/LabVIEW-CLI/releases/tag/v1.4.0 (the VI Package is available on the LabVIEW Tools Network VIPM repository, but currently you need to manually run the msi installer)
https://github.com/NISystemsEngineering/LV-JUnit/releases/tag/1.0.1 (now also available on the LabVIEW Tools Network VIPM repository)
https://github.com/LabVIEW-DCAF/UTF-Test/releases/tag/1.0 (now also available on the LabVIEW Tools Network VIPM repository)
The VI Package included here

Groovy scripts assume that C:\Users\Public\Documents\National Instruments\LV-CLI Common Steps\steps is mapped to the L:\ drive.