Sign Up


Our team is trying to automate building of VI Packages in our Gitlab CI/CD pipeline. I have had success in programmatically building packages when done under a regular interactive Windows user account, but the same script will fail to build when run under the SYSTEM account (which is the default behavior of the Gitlab Runner, since that is itself a Windows service).

The failures are reported as missing VIs, when the VIs clearly exist. So it seems that somehow the VI Package Builder doesn't seem to understand how to find the VIs when running under the SYSTEM account.

Has anyone else encountered this behavior? Are there any known workarounds?


Please sign in to leave a comment.