This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

activity log
Every plan has an activity log. An activity log is a temporary display of the latest output from the plan's most recent build log.
artifact
An artifact (e.g. a JAR file) is something created by a build. A build's artifacts are specified in the build's plan by a Bamboo administrator.
author
An author is any person who checks-in code to a repository that is associated with a Bamboo plan. An author need not be a Bamboo user.
build

A build is one execution of a plan.

Every build has a Build Number, which is appended to the relevant Plan Key to form the Build Key. For example, if a plan with the key "CRM-BRANCH" is executed for the seventeenth time, the build key will be "CRM-BRANCH-17".
build activity
Build activity is the number of builds that occur in a given period of time.
build duration
Build duration is the total time taken to execute a build plan — that is, the time taken to compile the code and run all of the plan's tests.

Variations in a plan's build duration can be monitored over time.
build log
Every build has a build log. A build log is a permanent record of all the output generated by compiling the plan's source-code and executing the tests.
build plan
See plan.
build queue
build result

Every completed build has a build result:

  • 'Successful' — the code compiled, with or without errors, and all tests completed successfully.
  • 'Failed' — either the code did not compile, or at least one test failed.

Additionally,

  • if the build result is 'Failed', and the previous build result was 'Successful', the build is said to be 'Broken'.
  • if the build result is 'Successful', and the previous build result was 'Failed', the build is said to be 'Fixed'.
build telemetry

Build telemetry is the insight provided by Bamboo's dynamic reports, charts and collation of build metrics. Build telemetry helps identify trends across build plans and across authors — not just focusing on the results of a single build.

builder
A builder is a software compiler program external to Bamboo. Bamboo supports multiple builders. Once a builder is defined in the Bamboo system, it can then be specified in build plans by a Bamboo administrator.
label

A label is a convenient way to tag and group build results that are logically related to each other. Labels can also be used to define RSS feeds.

Labels can be applied to build results automatically, by specifying the label(s) in a build plan (note that only Bamboo administrators can do this). Labels can also be applied ad-hoc to build results by Bamboo users.
plan

A Bamboo plan (or build plan) is the "recipe" for a build.

A plan defines: what gets built (i.e. the source-code repository); how the build is triggered; which builder to use; what tests to run; what artifacts the build will produce; who will be notified of the build result; and any labels with which the build result or build artifacts will be tagged.

Every plan belongs to a project.



Each plan has a Plan Key, which is prefixed by the relevant Project Key. E.g. the "CRM" project could have plans "CRM-TRUNK" and "CRM-BRANCH".

Projects and plans can only be configured by Bamboo administrators.
project
A project is a collection of plans.

A project enables easy identification of plans that are logically related to each other, which is useful for instance when generating reports across multiple plans.

Each project has a Name (e.g. "CRM System") and a Key (e.g. "CRM"). The Project Key is prefixed to the relevant Plan Keys, e.g. the "CRM" project could have plans "CRM-TRUNK" and "CRM-BRANCH".

triggering


There are a variety of ways in which a build can be triggered for a plan:

  • Code updated — a build can be triggered whenever one or more authors checks-in code.
  • Scheduled build — a build can be scheduled to occur at regular intervals.
  • Dependency — a build can be triggered whenever a successful build occurs for another plan.
  • Manual build — a build can be triggered manually.
  • Initial clean build — a build will be triggered when a new plan is created.

The way in which each build was triggered is listed in the 'Reason' column on the Dashboard.

 
Note that build triggering can only be configured by a Bamboo administrator.

Return to Bamboo Documentation

  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

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