Documentation for Bamboo 4.2.x. Documentation for other versions of Bamboo is available too.

Bamboo でトリガーすると、計画ビルドを自動的に開始できます。Bamboo には次のトリガー メソッドがあります。

  • リポジトリをポーリングして変更を確認する — Bamboo は、定期的に、またはスケジュールに従って、変更に対してソース リポジトリをポーリングします。これにより、計画のソース リポジトリでコードが変更された場合にのみ、計画ビルドが実行されます。
  • 変更がコミットされるとリポジトリがビルドをトリガーする — ソース リポジトリが Bamboo にイベントを発生させるように設定されている必要があります。これには、Bamboo サーバーの負荷を最小限に抑えるという利点があります。
  • Cron を使用したスケジューリング — コードが変更されたかどうかに関係なく、ビルドはスケジュールに従って実行されます。これにより、予測可能なスケジュールに沿ってチームが日付を設定できます。
  • 毎日 1 回のビルド — 毎日指定された時間にビルドが実行されます。

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

説明

リポジトリをポーリングして変更を確認する

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.

変更がコミットされるとリポジトリがビルドをトリガーする

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.

  • This option minimises server load, because message events are sent only when code changes to a repository are committed.
  • You must configure your source code management system to send message events to Bamboo about code changes in the repositories.

See Repository triggers the build when changes are committed.

Cron ベースのスケジューリング

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.

毎日 1 回のビルド

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.

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.

条件付きビルド トリガー

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.

ビルド トリガー条件を指定するには、次の手順に従います。

  1. ダッシュボードをクリックし、すべてのプラン タブをクリックします。
  2. Locate the plan in the list and click the edit icon  to display the plan's configuration pages.
  3. Click the Plan Details tab.
  4. Select Only run Build if other Plans are currently passing, under 'Trigger Conditions'.
  5. 完全なキーを追加して、他のプランを 1 つ以上指定します。

  • ラベルなし


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.