Advanced usage of TestStand Deployment Utility

[ChrisMatheson]

I would like to automate the build process for my test stand systems.

Is there a way to call and build a .tsd automatically from labview or command line?

Alternatively is there a way to call post actions after a successfully completed build (i.e.. Zip and move files etc etc)

Any help or pointers would be greatly appreciated.

Chris

[chenny · Accepted solution]

I don't think you can automatically create a tsd.

But once you have a tsd file, you can automate the deployment process by cmd line such as "DeploymentUtility.exe path" -build "tsd_file_path"

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

Others such as zip or move files are very basic, you can do it using any script language

CmtGetCurrentThreadID()

[RayFarmer]

Hi,

That is not possible, as chenny points out, even looking in the Tools folder for the deployment tool, there doesn't look to be any source code to make you own changes.

Maybe you should make a suggestion at NI TestStand Idea Exchange.

[ChrisMatheson]

Thanks for this help. The switches for the deployment utility are helpfull, i dont guess you have a full rundown of all the options? 

Chris

[RayFarmer]

I have looked in the TestStand Help - Deploy TestStand Systems and there is nothing mentioned.

[Callie]

Refer to the TestStand Deployment Utility topic and related deployment utility dialog box topics in the NI TestStand Help.

Please let me know if you have any other questions.

Thanks,

Callie Jones

TestStand Documentation Team

[RayFarmer]

Callie,

I have been right the way through the TestStand Deployment Utility and through the NI TestStand Help and can find no mention of the argument switches used with the deployment tool.

Maybe you would like to point to the actual chapter or some where else where this information is available.

[AllenP]

None of the switches are officially supported and are subject to change at any point.  I do think that actually supporting and documenting switches is a good idea, though!