This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

There are a number of methods by which Bamboo can 'trigger' (i.e. execute) a Plan's build,
  • Build Strategy:
    • Code updated — a Plan's build is triggered whenever one or more authors checks in code.
    • Scheduled build — a Plan's build is triggered at scheduled times or specified time intervals.
    • Manual build — a Plan's build is only ever triggered manually.
    • Initial clean build — a Plan's build is triggered immediately after a new Plan has been created.
  • Build Dependency:
    • Dependency — a build can be triggered whenever another Plan's build is successfully completed.

The trigger method for a Plan's build is listed in the 'Reason' column on the Dashboard.

On this page:

Build Dependencies and Build Strategies

Build dependencies are "parent-child" relationships between Plan builds, which can be configured for triggering a series of Plan's builds. See Setting up 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 such a case, builds of Plan A will be triggered when code changes are detected in its repository as well as 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 & dependent builds only as the build strategy for your plan. See Triggering a Plan Build Manually.

Considerations for choosing a Build Strategy

Code Updated

"Triggering a Plan's build when code is updated" ensures that a Plan build only occurs when something changes in the Plan's source repository (which may affect the outcome of a Plan build). There are two ways to trigger a Plan's build when code is updated:
  • "Pull strategy" — "Polling the Repository for changes" means that Bamboo will check out the source code on a regular basis and examine it for changes. If Bamboo detects a change, Bamboo triggers a build of your Plan. See Polling the Repository for Changes.
  • "Push strategy" — "Repository triggers the build when changes are committed" has the advantage of placing minimal load on your Bamboo server. However, it requires that your source repository is configured to fire an event to the Bamboo server (which the configured Plan will 'listen for'). See Repository Triggers the Build when Changes are Committed.

Scheduled Build

"Triggering a Plan build based on a schedule" can allow a team to structure the day according to a predictable schedule. Note that scheduled builds are run regardless of whether or not any code changes have occurred. There are two ways to schedule a build:
  • Single Daily Build — A "Single daily build" runs at a time of your choice. This is particularly suitable for builds that take a long time to complete. See Single Daily Build.
  • Cron-Based Scheduling — "Cron Based Scheduling" allows you to run builds based on a schedule. This schedule can be configured using a Cron expression or via the Schedule Editor.

    The schedule can be daily (times per day), weekly (days per week), monthly (days per month) or based on a Cron expression.

     See Cron Based Scheduling.

Manual and Dependent Builds

Triggering a build manually or by build dependencies allows you to ensure that builds are only triggered manually or by parent builds of dependent builds (as described in the 'Build Dependencies and Build Strategies' section above). See Triggering a Plan Build Manually.

関連トピック

For more information on triggering Plan builds, see the following topics:

Triggering a Plan Build when Code is Updated
Triggering a Plan Build Based on a Schedule
Triggering a Plan Build Manually
  • ラベルなし



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.