This page describes how to configure a Bamboo task to run a script. The Script task is flexible enough to allow the possibility to use: the default shells on Linux (/bin/sh) or Windows (cmd.exe), a more modern shell on Windows (Powershell), and an arbitrary shell in Linux by using the shebang on the first line of the script file. This can be controlled by the Interpreter field explained below.
To configure a script task:
- Go to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
- Select the name of the desired script task, or select Add task > Script if creating a new task.
Complete the following settings:
A description of the task, which is displayed in Bamboo.
Disable this task
Check or clear to selectively run this task.
Add condition to task
Make task run only when a certain condition is met.
You can find conditions on Atlassian Marketplace or implement your own.
Make sure to use the syntax appropriate for the interpreter of your choice. You can select from the following interpreters:
This option selects the interpreter based on the first line of the script, typically using the shebang.
- Windows PowerShell
This option uses the Powershell on Windows.
- /bin/sh or cmd.exe
This option uses the default shell of the operating system (sh for Linux, cmd.exe for Windows).
Select the location of the script file.
- File — enter the location of the file in the Script file field. This can be either relative to the repository root of the plan, or absolute. You can include variables (see Bamboo variables).
- Inline — enter the script in the Script body field.
Specify an argument to pass to the script. Arguments that contain spaces must be quoted. You can include variables (see Bamboo variables).
If required, specify environment variables and working directory settings:
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 Bamboo variables).
Multiple variables should be separated with spaces. Parameters with spaces must be quoted (e.g ANT_OPTS="-Xms200m -Xmx700m").
Working subdirectory (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.
- Select Save.
Was this helpful?Yes Provide feedback about this article