When building any type of distribution it would be nice to have the following actions
1) Pre-Image Build Script -> Execute windows command or batch file
2) Post-Image Build -> Execute windows command or batch file
3) Post-Distribution Build -> Execute windows command or batch file
The purpose of the three entry points is to allow the user to preform actions of their choosing.
Action #1 is to be run just prior to Starting Analysis to allow the user to preform any automated actions prior to analyzing the build project.
Action #2 is to be run after the deployment image structure and all files are created on disk but before the distribution package is create. The purpose of this action is to allow the user to inject any files, update files, preform verification or hashing and so on. In my specific use case, I need to create a file that has relative paths and a hash value for each file being deployed. This process is automated but currently run manually prior to a package build.
Action #3 is to be run after the Distribution package is made. Automate any file steps such as uploading the file to a network location, or generating an automated email.
Each action should call the script with parameters such as path info, deployment name or provide a list of variables that users can choose to have added to the command line for each action.
If the action script or command returns a non-zero value the Build process should terminate.
Re-Posted from (https://forums.ni.com/t5/NI-TestStand/TestStand-Deployment-Utility-Scripts/td-p/4373139)
Brian G. Shea
Former Certified LabVIEW Architect
