Execute script

Overview of the Execute script job step, which allows for executing shell scripts.

Figure 1. Execute script job step

The Execute script job step makes it possible to run shell scripts during a job. From the job step settings (Figure 1), you can customize information about the job step, including:

  • A custom step name can be defined; otherwise, the default step name will be used
  • Execution type: This can be a Shell script or a batch command.
  • Job execution: Enter the Execution command which should be executed. Next to the Job execution field, button enables text wrapping of the commands entered in the field.
  • Every step has Advanced options through which steps can be managed. When execution of the step fails, execution of the job continues. If option Abort job on step fail is marked, Job execution will stop once this step fails and further steps will not be executed. When it comes to skip condition, it allows skipping the current step if the condition is met.
    Figure 2. Execute script job step with advanced options shown
Note: In order to save a form, all input fields must be valid. Required fields are signed with *.
Note: When script finishes its execution, it will result with a status code. This code is an integer value that represents a response from the OS that reports success, an error or another condition that provides a clue about what caused an unexpected result from the executed command or script. For example, if the script finishes successfully OS will result with status code 0, which means that your command/script has executed and exited without any problems or errors.