Command Line

Using the Command Line build runner, you can run any script supported by the OS.

Command Line Runner Settings

Option	Description
Working directory	Specify the working directory where the command is to be run (if it differs from the build checkout directory ).
Run	Specify the mode: run an executable with parameters or run custom shell/batch script (see below).
Command executable	The option is available if "Executable with parameters" is selected in the Run* drop-down menu.* Specify the path to an executable to be started.
Command parameters	The option is available if "Executable with parameters" is selected in the Run* drop-down menu.* Specify space-separated parameters to pass to the executable. If a parameter contains a space, it can be enclosed in double quotes. For non-trivial parameters it is recommended to use "Custom script" option instead.
Custom script	The option is available if "Custom script" is selected in the Run* drop-down menu.* A platform-specific script which will be executed as an executable script in Unix-like environments and as a `*.cmd` batch file on Windows. Under Unix-like OS the script is saved with the executable bit set and is then executed by OS. This defaults to /bin/sh interpreter on the most systems. If you need a specific interpreter to be used, specify shebang (for example, `#!/bin/bash`) as the first line of the script.
Format stderr output as:	Specify how the error output is handled by the runner: error: any output to `stderr` is handled as an error warning: default; any output to `stderr` is handled as a warning

In this section, you can specify a Docker image which will be used to run this build step.

To learn about configuring code coverage options, refer to the Configuring Java Code Coverage page.

Last modified: 05 March 2021