There are several methods by which Bamboo can 'trigger' (i.e. begin executing) a plan's build: Build Strategy
Build Dependency
The trigger method for a plan's build is listed in the 'Reason' column on the dashboard. |
Considerations for choosing a build strategy
This table lists Bamboo's available 'build strategies', which determine how the execution of a plan (i.e. a build) is triggered. You set a Build Strategy option on the Plan Details tab of the plan configuration.
Build strategy option | Description | Reason for choosing | |
---|---|---|---|
Code is updated | Polling the Repository for changes | Bamboo will 'poll' the source code repository for changes based on either of the following:
If Bamboo detects a change to any code in this repository, a build of this plan will be triggered. |
|
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. See Repository triggers the build when changes are committed. |
| |
Scheduled | Cron Based Scheduling | Bamboo will trigger a build of this plan based on a cron expression. |
|
Single daily build | Bamboo will trigger a build of this plan once per day at a specified time. See Single daily build. |
| |
Manual | Manual | Bamboo only triggers a build of this plan when the user chooses this function manually or through a build dependency. |
|
Build dependencies and build strategies
Build dependencies are "parent-child" relationships between plan builds, which can be configured so that a series of plan's builds are triggered. See Setting up plan build dependencies.
Build dependencies work together with the build strategies of plans to trigger builds of these plans. For example, you can set up Plan A to poll its repository for changes as well as configure a build dependency on a parent plan (Plan B). In this case, builds of Plan A will be triggered when code changes are detected in its repository and also when builds of Plan B complete successfully.
If you want your builds to only be triggered by successful parent builds from your build dependencies, you can do this by specifying Manual as the build strategy for your plan. See Triggering a plan build manually.
Conditional build triggers
This field is only available when configuring an existing plan.
You can choose to run builds of this plan only if other specified plans are currently passing. Those plans that must build successfully before this plan can be built. See also Setting up plan build dependencies.
To specify build trigger conditions:
- Click Dashboard and then the All Plans tab.
- Locate the plan in the list and click the edit icon
to display the plan's configuration pages.
- Click the Plan Details tab.
- Select Only run Build if other Plans are currently passing, under 'Trigger Conditions'.
- Specify one or more other plans by adding their full keys.