Best way to run teststand from any location

[Torpedotown]

We are trying to use LabVIEW & TestStand in a Continuous Integration scenario.

This involves the system being able to run from any specified file system location.

Whats the best method to achieve this?

Is it using the subst command to map a viurtual file system, using totally relative TestStand paths or using the deployment method.

Currenlty the system uses a single top-level path with all sequences set with relative paths from that.

It seems that moving to another file location requires adjustment of several ini files and writing to the registry to relocate the config file directory.

I think this also mandates that LabVIEW recompiles the VI's before running.

We are not restriced to a deploment only TestStand license.

Regards, Torpedotown

[NI-MarkN]

Hi Torpedotown,

The most appropriate way of doing it is most likely going to be with the help of TestStand Deployment Utility. It's got a fairly simple command line API which you could use to do all of your integration.

You can use it for building deployments and installers, for example: 

Once you have a tsd file, you can automate the deployment process by cmd line such as "<path_to_the_executable>/DeploymentUtility.exe" build "example_file.tsd"

After deployment, you can check DeploymentUtility.log in your cfg folder to figure out whether the build is successful or not.