This is the documentation for Bamboo 5.6. View this page for the

Unknown macro: {spacejump}

of Bamboo, or visit the latest Bamboo documentation.

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.

  • Your VCS must service a 'check out' or 'update' command whenever it is polled, even if no code has changed in a repository.

See Polling the repository for changes.

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.

  • 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 repositories.

See Cron-based scheduling.

Single daily build

Bamboo will trigger a build of the plan once per day at a specified time.

  • Can be set up to run at a time of you choice.
  • 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 repositories.

See Single daily build.
  • No labels

 

 

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