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; 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.
Every plan belongs to a project.
-
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".
Note that creating a new project only requires defining the Project Name and Project Key, which is (optionally) done as part of the process of creating a new plan.
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".
Each plan's build results are stored in a subdirectory under your 'Build Directory' (see 7.1 Locating Important Directories and Files).
RELATED TOPICS
Bamboo 1.2 Documentation Home
1.1 About Projects, Plans and Builds
