[Bamboo Knowledge Base]
This page describes how to configure a Bamboo task that uses a command (e.g. Bash) executable.
See Configuring a builder task for an overview of Bamboo builder tasks.
To configure a command task:
Complete the following settings:
|Task Description||A description of the task, which is displayed in Bamboo.|
|DIsable this task||Check, or clear, to selectively run this task.|
The command executable that is available to perform the task (e.g. Bash). The executable that you select will become one of the task's (and so, the job's) requirements.
You can add other executables, if required.
|Argument||(Optional) The relevant argument to pass to the command. Note that arguments which contain spaces must be quoted. You can include variables (see Bamboo variables).|
|Environment Variables||(Optional) Additional system environment variables that you want to pass to your build. Note that existing environment variables are automatically available to the executable. You can also include Bamboo global or build-specific variables (see Using global, plan or build-specific variables).|
Multiple variables should be separated with spaces. Parameters with spaces must be quoted (e.g ANT_OPTS="-Xms200m -Xmx700m").
|Working Sub Directory||(Optional) An alternative subdirectory, relative to the job's root directory, where Bamboo will run the executable. The root directory contains everything checked out from the job's configured source repository. If you leave this field blank, Bamboo will look for build files in the root directory. This option is useful if your task has a build script in a subdirectory and the executable needs to be run from within that subdirectory.|