A Plan defines everything about your entire build process. Plans:
- consist of one or more Jobs, which are organised into one or more Stages;
- contains a single 'Default Job' in a single Stage, after creating a new Plan;
- define default settings for what gets built by Jobs in the Plan (i.e. the 'default source repository');
- define how the Plan's build is triggered;
- who will be notified of the Job's build result;
- define who has permission to view and perform various actions on the Plan and its Jobs.
Every plan belongs to a Project.
Projects and plans can only be configured by Bamboo administrators (see Creating a Plan).
Creating a Plan
始める前に
To create a Plan in Bamboo:
- Click the Create Plan link in the top navigation bar. The Create Plan introductory page is displayed with the following options:
- Click one of the options to start creating your Plan. Each of these options is described in the sections below.

Screenshot above: Create Plan Introductory Page
Create a New Plan
When you create a new Plan, you can define everything about your build process, including what gets built, how the Plan's Build is triggered and what Jobs are executed.
On the 'Create a New Plan' page, complete the options in the following sections to create your Plan:
- In the Plan Details section, enter or select the relevant items for the following fields:
- Project — Select an existing project to which this Plan will belong. If this field is not available (because no projects have yet been defined on your Bamboo server) or you select 'New Project', complete the following fields:
- Project Name — Enter a name for a new project or select an existing project. The plan which you create on this page will be associated with this project.
- Project Key — Enter a unique key for this project or select an existing project key.
- Plan Name — Enter a name for the new Plan.
- Plan Key — Enter a unique key for the new Plan.
- Plan Description — Enter a short sentence to describe this Plan.
- In the Source Repository section, specify a source repository configuration that will initially be used for building this Plan's Default Job and also defines the default source repository (or Plan's repository), which Jobs in this Plan can inherit.
For details, refer to the following source repository configuration procedures (from step 4), since many of these fields and options change depending on the 'Repository' you select:
- In the Build Strategy section, select or enter the relevant items for the following fields:
- Build Strategy — Choose one of the Build Strategy options (listed below), which will be used for triggering the execution of this plan.
You may need to configure other fields specific to your chosen build strategy.
- In Builder Configuration section, specify the builder configuration that will be used for building the Plan's Default Job. The builder that you select will become one of this Job's requirements. For details please see Configuring a Job's Requirements.
Refer to the following documentation on Bamboo's builders (from step 2) for details about these options, since many of these fields and options change depending on the 'Builder' you select.
- In the Enable this plan section, choose whether or not to enable this Plan. Enabling the Plan instructs Bamboo to commence executing builds of the Plan based on the Plan's Build Strategy (defined above). To enable this Plan, select the 'Yes please!' check box.
- Click the 'Create' button to create the Plan and the Plan's Plan Summary page will be displayed.
When you next return to the Dashboard (by clicking 'Home' in the top left of the page), your new Plan (and new Project, if applicable) will be displayed in the 'All Projects' list. Bamboo will also automatically run an initial build for your new Plan, unless you have opted for the Manual & dependent builds only Build Strategy.
If you wish to configure more Plan options, please refer to Editing a Plan.
注意
Clone an Existing Plan
When you clone an existing Plan, you make a copy of that Plan and its entire configuration.
On the 'Clone and Existing Plan' page, complete the options in the following sections to clone an existing Plan:
- In the 'Plan to clone' section and dropdown, select the Plan you wish to clone. Plans are listed in the format 'Project Name - Plan Name' and are organised by Project.
Only Plans for which you have the 'Clone' and/or 'Admin' plan permission are shown.
- In the 'Plan Details' section, enter or select the relevant items for the following fields:
- Project — Select an existing project to which this Plan will belong. If this field is not available (because no projects have yet been defined on your Bamboo server) or you select 'New Project', complete the following fields:
- Project Name — Enter a name for a new project or select an existing project. The plan which you create on this page will be associated with this project.
- Project Key — Enter a unique key for this project or select an existing project key.
- Plan Name — Enter a name for the new Plan.
- Plan Key — Enter a unique key for the new Plan.
- Plan Description — Enter a short sentence to describe this Plan.
- In the Enable this plan section, choose whether or not to enable this Plan. Enabling the Plan instructs Bamboo to commence executing builds of the Plan based on the Plan's Build Strategy (defined above). To enable this Plan, select the 'Yes please!' check box.
- Click the 'Create' button to create the Plan and the Plan's Plan Summary page will be displayed.
When you next return to the Dashboard (by clicking 'Home' in the top left of the page), your new Plan (and new Project, if applicable) will be displayed in the 'All Projects' list. Bamboo will also automatically run an initial build for your new plan, unless the Plan you cloned uses the Manual & dependent builds only Build Strategy.
If you wish to configure more Plan options, please refer to Editing a Plan.
注意
- You can configure Bamboo to automatically start an initial build for a new Plan, even if the Plan you cloned uses the Manual & dependent builds only Build Strategy. To do so, add the
fire.initial.build.for.manual.strategy
to your bamboo.cfg.xml file as described in Configuring System Properties.
Import a Maven 2 Project
If you have the details for a Plan set up in your Maven 2 project, Bamboo can check out and parse the pom.xml
from this project and create a new Plan using the details from it. This feature will not work with Maven 1 projects.
*To create a new Plan from a Maven 2 pom.xml
file:*
- Specify a source repository configuration that will initially be used for building this Plan's Default Job and also defines the 'default source repository' (or Plan's repository), which Jobs in this Plan can inherit.
For details, refer to the following source repository configuration procedures (from step 4), since many of these fields and options change depending on the 'Repository' you select:
- CVS
- Subversion
- perforce
- Mercurial
If you specify a CVS or Subversion source code management system, then the location you configure in the respective CVS Root or Repository URL fields should contain your Maven 2 project's pom.xml
file.
- Click the 'Import' button to display the Confirm Plan Details page.
- On the Confirm Plan Details page, some of the fields should already have been populated with information from your
pom.xml
file. Confirm the following (making any necessary modifications):
- Plan Details in the top section of the page — for more information about these fields, refer to the Plan Details section in the Create a New Plan procedure above.
- Source Repository — for more information about these fields, refer to step 1 of this procedure.
- In the Enable this plan section, choose whether or not to enable this Plan. Enabling the Plan instructs Bamboo to commence executing builds of the Plan based on the Plan's Build Strategy (defined above). To enable this Plan, select the 'Yes please!' check box.
- Click the 'Confirm' button to save your Plan configuration so far and the Builder tab of the Plan's Default Job is displayed.
- Select the type of 'Builder' that will be used for building this Default Job.
In practice, you should leave the Builder option set to your 'Maven 2' builder and configure the options on this page as described in Bamboo's Maven configuration documentation. You can select another builder here but this would only be useful if your Maven 2 project's pom.xml
depended on a non-Maven 2 builder. If you do need to specify a non-Maven 2 builder, refer to the Builder Configuration section in the Create a New Plan procedure above.
If you wish to configure more Plan options, please refer to Editing a Plan.
注意
- Security Manager settings too strict — Please note, during the Maven import process, the project file (
pom.xml
or other specified by the user) is analysed using the maven-embedder library. The parent POM files will be examined in the local repository or downloaded from network repositories. In order to reuse Maven's credentials for the network repositories, Bamboo requires internal access to the maven-embedder. If your JVM's or web container's SecurityManager settings are too strict, this process will fail and you will see an error similar to the following in your Bamboo logs:
"Problem while initializing Maven Embedder. Probably Security Manager settings are too strict, refer to http://tomcat.apache.org/tomcat-6.0-doc/security-manager-howto.html"
If your imported Maven project file uses repositories that require credentials (i.e. not public or local), you will need to adjust the SecurityManager settings for your JVM or web container appropriately for the import to work.
- By default, all Plans created by importing a Maven 2 project use the Polling the Repository for changes Build Strategy, below, which you can later change when editing this Plan. You can configure Bamboo to automatically start an initial build for a new Plan, even if you have selected the Manual & dependent builds only Build Strategy. To do so, add the
fire.initial.build.for.manual.strategy
to your bamboo.cfg.xml file as described in Configuring System Properties.
Appendix - Build Strategies
This table lists Bamboo's available build strategies that determine how the execution of a plan (i.e. a build) is triggered. Each build strategy has other options (listed at the far right of this table), which may also require configuration.
Build strategy option |
説明 |
Reason for choosing |
Other build strategy-specific options |
Polling the Repository for changes |
Bamboo will 'poll' the source code repository (specified above) at regular intervals. If Bamboo detects a change to any code in this repository, a build of this plan will be triggered. |
This is the simplest option as it requires no further configuration. However, for every plan that uses this build strategy option, your source code management system must service either a 'check out' or 'update' command at the specified polling frequency (right), even if no code has changed in the repository. |
Polling Frequency (in seconds) Defines the interval between each poll for this plan. |
The repository triggers the build when changes are committed |
Bamboo will wait to receive a message from the source code repository (specified above) about any code changes in this repository. When Bamboo receives such a message, Bamboo will trigger a build of this plan. |
This option minimises server load as message events are sent only when code changes to this repository are committed. However, you must configure your source code management system to send message events to Bamboo about code changes in this repository. |
Trigger IP Address Use only if you need to specify an IP address which is different from that of the source code repository's server. |
Cron Based Scheduling |
Bamboo will trigger a build of this plan based on a Cron expression. |
This option allows you to schedule builds when server load is likely to be minimal, for example, outside office hours. Scheduled builds are triggered irrespective of any code changes in the source code repository. |
Cron Expression Consists of 6 mandatory and one optional field in the order: seconds, minutes, hours, day-of-month, month, day-of-week and (optional) year. For more information about Cron expressions, please refer to How do I construct a cron expression in Bamboo? |
毎日 1 回のビルド |
Bamboo will trigger a build of this plan once per day at a specified time. |
This option is suitable if a build of this plan takes a long time to complete. Scheduled builds are triggered irrespective of any code changes in the source code repository. |
Build Time The time in 24-hour format (hh:mm) at which Bamboo will trigger a build of this plan. |
Manual & dependent builds only |
Bamboo only triggers a build of this plan when the user chooses this function manually or through a build dependency. |
This option is suitable if a build of this plan will fail, perhaps due to source code problems of failing tests. This frees up Bamboo agents to build other plans which are less likely to fail. |
There are no other options to configure for this build strategy. |