Step properties specify how to execute a step, handle its output, and what to do upon completion. A step command can also execute another project or library.
If a step property is not set explicitly, its value is inherited from the project.
Choosing Project Default causes the step to inherit the access properties of the project.
Enter one or more operating system commands, subject to the following guidelines:
Separate individual commands by placing them on separate lines.
All the commands in a single step are executed on one server. If you want to be able to thread commands across multiple servers, you must place those commands in separate steps.
If you use more than one command in step, you may want to use command filters as the step's Result property. When you use the default Exit Code setting for the Result property of your step, the success or failure of the entire step is determined by the last command in the step. Earlier commands may succeed or fail, but the system only looks at the exit code of the last command. When you use a filter, you can catch failures in earlier commands.
You can enter multiple commands.
#!cmd.exe /CNote that the /C option is required for cmd.exe as otherwise it waits for additional commands after your step commands are delivered to it. You might use the #!/bin/perl command on a UNIX or Linux machine.
Environment: Choose an environment. The system applies the values in the environment you select before it runs the command. The final environment depends on inheritance from the server and project variables as well as the step variables.
Choosing Project Default causes the step to inherit the environment of the project.
Set this property to Yes to allow threading of this step (running the step in parallel with other steps). Set the property to No to avoid threading. Set the property to Join to separate threaded blocks of steps. The first set of steps must complete before the next set of threaded steps following the Join step can start.