This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

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; which agent capabilities are required for the build ; what artifacts the build will produce; what tests to run; who will be notified of the build result; any labels with which the build result or build artifacts will be tagged; and who has permission to view and perform various actions on a plan and its build results.

A project is a collection of plans. Projects enable you to easily group and identify plans which are logically related to each other. They are especially useful when generating reports across multiple plans.

Each project has a Name (e.g. "CRM System") and a Key (e.g. "CRM"). The Key of a project prefixes the Keys of plans associated with that project - for example, the "CRM" project could have plans "CRM-TRUNK" and "CRM-BRANCH".

Every Bamboo plan is listed on the Dashboard, from where you can:

Projects and plans can only be configured by Bamboo administrators. Please see the Bamboo Administrator's Guide for details.



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

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