07-06-2011 10:05 AM
I'm trying to automate our use of the deployment utility by deploying from a .tsd file and calling the deployment utility from the command line. (See here) When I call the utility, it opens the correct .tsd file, but does not do the build. I am including the "-build" switch, but it doesn't build. The build executes just fine if I then click "Build".
The command I'm running is:
"C:\Program Files\National Instruments\Teststand 2010\Components\Tools\Deployment Utility\DeploymentUtility.exe"-build "C:\mydeployment.tsd"
Any ideas why the build isn't happening?
-Joe
Solved! Go to Solution.
07-06-2011 01:15 PM
What does the log file in /cfg say?
07-06-2011 02:03 PM - edited 07-06-2011 02:04 PM
I'm running TS 2010, so I think the log file is now "TSDU Detailed Status Log.txt" located in user\Local Settings\Temp. If I'm looking at the wrong file, let me know.
I ran this command: "deploymentutility.exe -build J:\mydeployment.tsd" from
C:\Program Files\National Instruments\TestStand 2010\Components\Tools\Deployment Utility
The deployment utility displays the .tsd file, and then nothing happens. At this point, the log file contains:
7/6/2011 2:49:13 PM:Loading build file:
J:\mydeployment.tsd
7/6/2011 2:49:13 PM:Starting a log for the deployment.
7/6/2011 2:49:13 PM: Operating System: Windows XP
7/6/2011 2:49:13 PM:TestStand Version: 2010 (4.5.0.310)
If I then click the "build" button, the build proceeds, and completes without error. At this point, the log file contains:
7/6/2011 2:49:13 PM:Loading build file:
J:\mydeployment.tsd
7/6/2011 2:49:13 PM:Starting a log for the deployment.
7/6/2011 2:49:13 PM: Operating System: Windows XP
7/6/2011 2:49:13 PM:TestStand Version: 2010 (4.5.0.310)
7/6/2011 2:58:41 PM:Starting Analysis
7/6/2011 2:58:41 PM: Processing directoryJ:\SandboxWS\Develop
7/6/2011 2:58:41 PM: Done processing directoryJ:\SandboxWS\Develop
7/6/2011 2:58:42 PM:Finished Analysis
7/6/2011 2:58:42 PM:Building...2:58 PM
7/6/2011 2:58:42 PM:LabVIEW Version: 10.0.1 (2010 SP1) (32-bit) English
7/6/2011 2:59:12 PM:List of source files and their destinations on the build:
{trimmed file path messages for privacy reasons}
7/6/2011 2:59:16 PM:The build is finished
2:59 PM
7/6/2011 2:59:16 PM:+++++++++++++++++++++++++++++++++++++++
07-06-2011 03:05 PM
Are you running the command as an admin? I've seen where the Deployment Utility won't proceed when it can't delete a write-protected folder in a different user folder at the beginning of the build... Other than that I have no idea.
07-06-2011 03:18 PM
Yes, I'm an admin.
You had me wondering: The deployment was pointed to a Perforce workspace under source code control, so I thought maybe there were permissions issues there, but after changing the deploy location to an uncontrolled folder, I still have the same issue.
Anyone else have any ideas?
07-11-2011 11:24 AM
Joe,
The build switch is just "build" not "-build". You should use:
"C:\Program Files\National Instruments\Teststand 2010\Components\Tools\Deployment Utility\DeploymentUtility.exe" build "C:\mydeployment.tsd"
Note:This is an undocumented internal feature we use for Testing the deployment utility. The interface is very limited- you can do a build but there is no way
to set parameters and no return value so you have to parse the log to determine if the build succeeded.
-Rick
07-12-2011 06:42 AM
YES, That's it! Thanks, Rick!
07-12-2011 11:13 AM
You're welcome.
-Rick Francis
04-03-2014 05:38 AM - edited 04-03-2014 05:39 AM
When i called the TestStand Deployment Utility from commandline, it launched the application and started building. Can i run this application silently. I am planning to automate this build process in a ContinuousIntegration environment (using Jenkins) so is there any way to run this in background? Any help would be appreciated. Thanks in advance
04-04-2014 03:45 PM
Hi Kalesh,
I can't think of any way to build from the command line silently. As Rick mentioned, this build from the command line process is undocumented and mostly just used by the TestStand developers.
You might also have more luck by posting to a new thread rather than one ~3 years old.
-Jim B.
Applications Engineer, National Instruments