NI Package Builder: Add command line option to set the package version

[JoGra]

Hi,

While trying to automate the building of packages of custom devices I found out that there was no practical way to automate what version the package should have (modifying the xml was not streightforward due to multiple namespaces)

The package builder manual shows "-v" command line option, but that will just print the version of the ni package builder itself. 

I want to propose that a "--set-version" command line option is added, which takes a "x.x.x.x" formatted string and would overwrite the <Version> tag in the .pbs file.  

Thank you!

[JoGra]

One comment - when creating packages in Labview, the normal set version VIs in the pre-build action do work. 
So somewhere in the package builder there is already some support for setting the package version.

[sdusing]

This is a must have for a package build tool like NI Package Builder. Please add ASAP

[Scott_Richardson]

An NI Package Builder solution file can be configured to build many packages and each might have unrelated versioning values and rules for auto incrementing. Is your need to override the auto-versioning and set the version of all packages to the same version, or only override a subset of the packages and potentially with different version values?

[sdusing]

I hadn't considered the multi-package building feature for NI Package builder. We want to use NI Package Builder to build VeriStand custom devices. We want to do this in a CI pipeline, where we would apply semantic versioning to the package within the pipeline script. In my view, it would be fine if the version of all packages built by the solution file were all the same. That's also the functionality that occurs in the MGI Solution Explorer when you build numerous packages, so it would be consistent across the NI ecosystem.