I'm currently trying to set up continuous integration with LabVIEW using Gitlab's continuous integration services. Here's my setup:
Windows 10 Virtual Machine
LabVIEW 2015
LabVIEW-CLI for LabVIEW/Command Line integration
Windows Powershell
GitLab Runner Service running as my administrator account
I'm trying to launch a LabVIEW VI from the command line that runs all the unit tests in the LabVIEW project contained within git directory of my current project.
The Problem
I can run the following command from powershell sucessfully:
PS C:\Users\diagonalley\Desktop\DA622\builds\0\project-0> labview-cli --lv-ver 2015 --verbose --kill '.\common-tools\source\run UTF tests.vi'
LabVIEW opens, loads the VI, runs my unit tests, and all is dandy. Here's the output:
Running the exact same command using the gitlab-runner service yields the following output:
LabVIEW opens and tries to load "run UTF tests" but fails and reverts to the getting started window:
The LabVIEW-cli never opens and my command times out. This is incredibly frustrating because LabVIEW gives me no indication as to why it can't open my VI, it just goes directly to the getting started window. Attempting to open the vi manually from the same getting started window works. Does anyone have any idea how to figure out why LabVIEW can't load my VI? There aren't any crash logs because LabVIEW isn't crashing. Any help would be greatly appreciated.
Cheers,