NI TestStand
TestStand package deployment installation directory
Solved!
I'm trying to streamline our NI deployment routine, and I'm having some trouble with TestStand Deployment Utility.
I'm creating a Package-Based Distribution: Single Package.
The problem I'm having is that when installing the package with the defined package installation destination: TestStand Public Documents Directory, I'm not getting the destination folder I'm expecting.
Instead of installing in the "TestStand 2023 (32-bit)" folder, the package installation creates a new folder called "TestStand 2023 Q4 (32-bit)"
Is there a way to edit how the deployment utility interprets the "TestStand Public Documents Directory"?
This would save me a lot of trouble, as I wouldn't have to change the folder naming scheme of our entire production test setup.
@Oli_Wachno wrote:
%TestStandPublic% is always linked to a folder with the TestStand Version.
Typing %TestStandPublic% in file explorer links to this folder:
NOT the Q4 folder.
@Oli_Wachno wrote:[ProgramData]\YourCustomStructHere
could be a workaround
Okay but how? These are my options:
chbo@mir-robots.com wrote:
@Oli_Wachno wrote:
%TestStandPublic% is always linked to a folder with the TestStand Version.
Typing %TestStandPublic% in file explorer links to this folder:
NOT the Q4 folder.
@Oli_Wachno wrote:[ProgramData]\YourCustomStructHere
could be a workaround
Okay but how? These are my options:
Haven't used the Package-based deployment from TestStand yet (been tinkering aroung with Package Builder lately).... just tried to look into it...
I don't see the option box like in your screenshot, when selecting Package Based-Single Package
Which TS version are you using?
Thats because you're looking in the wrong tab:
The Package distribution output directory only refers to the output of the .nipkg file.
Actually, the more I look into this the more confused I am..
In my environment variables:
It makes no sense to my why it doesn't use this folder, and instead creates a new folder with a different name.
Stupid me...
So the Package Builder seesm to offer more options compared to the deployment tool...
Nevertheless, most similar to what I intendend would be
From there, you can configure sub dir structure to your liking
@Oli_Wachno wrote:
Stupid me...
So the Package Builder seesm to offer more options compared to the deployment tool...
Nevertheless, most similar to what I intendend would be
From there, you can configure sub dir structure to your liking
Lovely! Just what I was looking for!
Doesn't explain the weird folder behavior, but it solves my issue.. hopefully.
I'll test it out and report my findings.
