Configuring tasks

A task:
  • Is a small discrete unit of work, such as source code checkout, executing a Maven goal, running a script, or parsing test results.
  • Is run sequentially within a job on a Bamboo working directory.

Tasks may make use of an executable if required. Tasks are configured within the scope of a job. A job can be configured to execute a number of tasks, on the same working directory. For example, before executing a Maven goal, the user could substitute specific files within the working directory, substitute version numbers, check out source repositories, or execute a script.

Final tasks for a job are always executed, even if previous tasks in the job failed.

Create a task for a job

When creating a new job or configuring an existing one, you need to specify the tasks that will execute the job's builds. You must specify an executable for each task. If you specify an Ant, Grails or Maven executable, you will also need to choose a JDK.

When creating a new plan, you can configure the tasks for the plan's default job.

To create a task for a job:

  1. Navigate to the tasks configuration for a job. Do this by:
  2. Click Add task.
  3. Click a task type, or search for a task.
  4. Click a particular task, such as 'SCP Task', then complete the form to configure the task. The fields in the form depend on thetask you chose. See the following pages for further details:
  5. Click Save.

Screenshot: Specifying a task for a job — Task types

Order the tasks in a job

Tasks can be designated as build tasks or final tasks in a job:

  • Build Tasks will run sequentially in the order specified in the job. If a Build Task fails, all subsequent tests will not be executed.
  • Final Tasks will run sequentially, once the build tasks have completed. Final Tasks will always be executed, regardless of whether any Build Tasks or other Final Tasks fail. Final Tasks will be executed even if you stopped the build manually.

To order the tasks for a job:

  1. Navigate to the tasks for the desired job.
  2. Drag and drop the tasks into the desired order in the table on the left. If you want to change a Build Task to a Final Task or vice versa, drag and drop it under the desired header in the table. Your changes will be saved immediately.

Screenshot: Existing Task — Command Task


  • Adding new executables — At least one executable is configured automatically after installing Bamboo. You can add more executables of different types as described in Configuring a new executable.
  • Adding new JDKs — At least one JDK is configured automatically after installing Bamboo. You can add more JDKs as described in Defining a new JDK capability.
  • About the 'Compatibility Task' — The 'Compatibility Task' is created by Bamboo when upgrading from Bamboo 3.0 or earlier and Bamboo cannot match a builder to a task. This may occur if you are using a builder enabled by a custom plugin.

Last modified on Feb 4, 2015

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.