This is the documentation for Bamboo 5.7. View this page for the

Unknown macro: {spacejump}

of Bamboo, or visit the latest Bamboo documentation.

The following pages contain information about configuring jobs and tasks for your Bamboo plans. If you are looking for information about Bamboo builds, please see Working with builds.

Jobs

A Bamboo job is a single build unit within a plan. One or more jobs can be organised into one or more stages. The jobs in a stage can all be run at the same time, if enough Bamboo agents are available. A job is made up of one or more tasks.

A job:

  • Processes a series of one or more tasks that are run sequentially on the same agent.
  • Controls the order in which tasks are performed.
  • Collects the requirements of individual tasks in the job, so that these requirements can be matched with agent capabilities.
  • Defines the artifacts that the build will produce.
  • Can only use artifacts produced in a previous stage.
  • Specifies any labels with which the build result or build artifacts will be tagged.

Each new plan created in Bamboo contains at least one job known as the 'Default Job'.

Projects and plans can only be configured by Bamboo administrators (see Creating a plan).

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, checkout source repositories or execute a script.

Screenshot: Configuring tasks for a job





  • No labels

 

 

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.