Enables a Jenkinsfile to specify 32- or 64-bit LabVIEW to build G code by specifying a map of versions to use instead of a string list. If a Jenkinsfile is already using the string list, it will continue to work using the 32-bit versions.
Build outputs will now reside one subdirectory lower than before. Instead of being archived to <LabVIEW version>/Built, they are now archived to <LabVIEW version>/x86/Built for 32-bit builds and <LabVIEW version>/x64/Built for 64-bit builds. The output location of packages (nipkg) does not change as part of this PR.
Why should this Pull Request be merged?
The VeriStand 2021 engine will be built with LabVIEW 64-bit, so the custom devices using these tools must also be built for 64-bit.
What testing has been done?
Built Embedded Data Logger, NI Synchronization custom device, and Routing and Faulting custom device to verify existing Jenkinsfiles still work and that the tools can build for both 32- and 64-bit LabVIEW in a single pipeline.
What does this Pull Request accomplish?
Enables a
Jenkinsfileto specify 32- or 64-bit LabVIEW to build G code by specifying a map of versions to use instead of a string list. If aJenkinsfileis already using the string list, it will continue to work using the 32-bit versions.Build outputs will now reside one subdirectory lower than before. Instead of being archived to
<LabVIEW version>/Built, they are now archived to<LabVIEW version>/x86/Builtfor 32-bit builds and<LabVIEW version>/x64/Builtfor 64-bit builds. The output location of packages (nipkg) does not change as part of this PR.Why should this Pull Request be merged?
The VeriStand 2021 engine will be built with LabVIEW 64-bit, so the custom devices using these tools must also be built for 64-bit.
What testing has been done?
Built Embedded Data Logger, NI Synchronization custom device, and Routing and Faulting custom device to verify existing
Jenkinsfiles still work and that the tools can build for both 32- and 64-bit LabVIEW in a single pipeline.