Sometimes it is necessary to debug SeqZap scripts on the Jenkins node where the test is run, usually because a specific piece of test hardware is only available on that node.
It is of course possible to start SeqZap Studio manually and open the test project, but to make this process even easier SeqZap’s command line interface (%SEQZAP_EXE%) supports the --studio argument which will start SeqZap Studio with the exact same arguments as the original call to %SEQZAP_EXE%.
This is especially useful when script files are referenced on the command line using --reference or when configuration properties are set using --set.
Adding the --studio argument each time it is needed is cumbersome, so usually the Jenkins job is parameterized so SeqZap Studio can be started when needed:
The command line argument to call SeqZap can then use this RUN_STUDIO environment variable to add --studio when needed:
