Index
Downloads (PDF, HTML & XML formats)
[Bamboo Knowledge Base Home]
Documentation for Bamboo 4.2.x. Documentation for other versions of Bamboo is available too. 
Triggering in Bamboo allows plan builds to be started automatically. Bamboo has the following trigger methods:
- Polling the repository for changes — Bamboo polls the source repository for changes, either periodically or according to a schedule. This ensures that a plan build only runs when code has changed in the plan's source repository.
- Repository triggers the build when changes are committed — Requires that your source repository is configured to fire an event to Bamboo. This has the advantage of placing minimal load on your Bamboo server.
- Cron-based scheduling — Builds are run according to a schedule, regardless of whether any code changes have occurred. This can allow a team to structure the day according to a predictable schedule.
- Single daily build — The build is run at a specified time every day.
Triggers can only be configured by a Bamboo administrator. The trigger method for a plan's build is listed in the 'Reason' column on the dashboard.
See also Running a plan build manually and Setting up plan build dependencies.
Considerations for choosing a build strategy
This table lists the ways in which plan builds can be triggered in Bamboo. Triggering option Description Polling the repository for changes Bamboo will 'poll' the selected source code repositories for code changes, using either a specified interval (that is, periodically) or a schedule. If Bamboo detects code changes, a build of the plan is triggered. Repository triggers the build when changes are committed Bamboo waits to receive a message about changed code from any of the selected source code repositories. When Bamboo receives such a message, a build of the plan is triggered. See Repository triggers the build when changes are committed. Cron-based scheduling Bamboo will trigger scheduled builds of this plan based on a cron expression. Single daily build Bamboo will trigger a build of the plan once per day at a specified time. See Single daily build.
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 trigger configuration 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 Running 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.
Overview
Content Tools
Apps
Log a request with our support team.
Raise an issue for our developers or tech writers.
See answers from the community.
Tweet, blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.