1.2 Creating a Plan

Only people with the 'Create' global permission can create a new build plan. 

There are two ways of creating a new plan: 

To create a new plan,

To copy an existing plan,

1. 'Plan Details'

Screenshot: 'Plan Details' 

• Project — When you create a new plan, you can either add it to an existing project or create a new project. Either:
  • Select the appropriate project from the drop-down list;
    or:
  • Select 'New Project' and complete the following two fields:
    1. Project Name — Type a descriptive name (e.g. 'Issue Tracking Application') that will identify your project on the Dashboard and in reports. 
    2. Project Key — Type a logical contraction of the Project Name (e.g. 'ITA'). The Project Key will be included in the plan's Build Results keys (e.g. 'ITA-MAIN-179'), so you may want to make it no longer than 3 or 4 characters. The Project Key must be unique within your Bamboo system.
• Build Plan Name — Type a name that will identify the plan within its project (e.g. 'Main Build', 'Branch', 'Unit Tests', 'Acceptance Tests'). Note that the Build Plan Name, which is displayed throughout Bamboo, is always accompanied by its Project Name.
• Build Plan Key — Type a logical contraction of the Build Plan Name. The Build Plan Key (e.g. 'MAIN') will be included in the plan's Build Results keys (e.g. 'ITA-MAIN-179'), so you may want to make it no longer than 3 or 4 characters. Note that the Build Plan Key only has to be unique within the project, that is, you could have a 'MAIN' plan in lots of different projects.
  

2. 'Source Repository'

Screenshot: 'Source Repository'

Here you need to specify what type of source-code repository this plan will use, where the repository is located, and what type of build strategy the plan will use. For details, please see:

• 1.7.1 CVS
• 1.7.2 Subversion
• 1.7.3 Perforce

CVS, Subversion and Perforce are supported out-of-the-box. If you need to use a different type of repository, you can write a Source Repository Module plugin to enable Bamboo to connect to your repository.

3. 'Builder Configuration'

Screenshot: 'Builder Configuration' 

Here you need to specify which builder Bamboo will use to build this plan. For details please see 2.1 Specifying a Plan's Build Resources.

One builder (Maven) is automatically configured when you install Bamboo. You can also define other builders (see 2.2 Configuring a new Builder) and then configure this plan to use them (see 2.1 Specifying a Plan's Build Resources).

4. 'Build Artifacts'

Screenshot: 'Build Artifacts'

Here you can define the plan's artifacts, e.g. JAR files which you wish to keep after each build.

Artifacts are copied to a subdirectory (/PLAN_KEY/download_data/) under your 'Build Directory' folder (see 7.1 Locating Important Directories and Files). Artifacts which you define in the plan are listed in each build result as User-defined artifacts (see 3.4 Viewing a Build's Artifacts in the Bamboo User's Guide).

For details, please see 1.8 Specifying a Plan's Build Artifacts.

5. 'Notifications'

Screenshot: 'Notifications' 

Here you can specify who will receive notifications about this plan's build results, and under what circumstances. For details please see 6.1 Enabling or disabling Notifications for a Plan.

6. 'Post Actions'

Screenshot: 'Post Actions' 

Here you can specify:

• what labels (if any) will be automatically applied to the plan's build results. For details please see 1.9 Specifying Labels for a Plan's Build Results.
• this plan's specific schedule for deletion of build results (if different to the default). For details please see 7.6.1 Specifying Expiry for a Plan's Build Results.

7. 'Permissions'

Screenshot: 'Permissions' 

Here you need to specify which users will be able to access the plan and its build results. For details please see 5.07 Granting Plan Permissions to Users or Groups.