このページの内容:

関連ページ:

Note that a plan that has no configured triggers can only be started manually, or if it is dependent on the successful build of another plan.

From Bamboo 4.3, you can configure multiple triggers for each plan. This allows a plan to be triggered by different trigger types, and to have triggering scenarios such as "every 5 minutes between 9:00am and 10:00am, and every 20 minutes between 1:00pm and 10:00pm".

Triggers can only be configured by a Bamboo administrator.

Choosing a triggering strategy

This table lists the ways in which plan builds can be triggered in Bamboo.

Triggering option

説明

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.

Conditional build triggers

This feature 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 must build successfully before this plan will be built. See also Setting up plan build dependencies.

Note that, because a plan may have multiple triggers configured, each of which can have differing trigger conditions, it is possible for the plan build to be started by one trigger, even though another trigger is currently blocked.

To specifybuild trigger conditions:

Choose Build > All build plans from the Bamboo header.

Locate the plan in the list and click the edit icon () to display the plan's configuration pages.

Click the Triggers tab, and click either an existing trigger or Add trigger.

Select Only run Build if other Plans are currently passing, under 'Trigger conditions'.