すべてのバージョン
Bamboo 5.13Bamboo 5.7.x
Bamboo 5.6.x
More...
The instructions on this page describe how to create a completely new Plan, i.e. not cloning an existing Plan or importing a Plan from Maven 2.
A Plan defines everything about your entire build process. Plans:
Every plan belongs to a Project.
Projects and plans can only be configured by Bamboo administrators (see Creating a Plan).
On this page:
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:
If you wish to configure more Plan options, please refer to Editing a Plan.
Screenshots above: Creating a new Plan - Plan configuration and Job configuration
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 |
Related documentation |
|---|---|---|---|
Polling the Repository for changes |
Bamboo will 'poll' the source code repository for changes based on set intervals or a schedule. If Bamboo detects a change to any code in this repository, a build of this plan will be triggered. |
This is the simplest option. However, this does mean that your SCM must service a 'check out' or 'update' command whenever it is polled, even if no code has changed in the repository. |
|
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. |
|
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. |
|
毎日 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. |
|
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. |
fire.initial.build.for.manual.strategy to your bamboo.cfg.xml file as described in Configuring System Properties.Creating a Plan
Cloning an Existing Plan
Importing a Plan from Maven 2