This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


  • 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".

    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 the 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 Locating Important Directories and Files).
  • No labels