_build strategies

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

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.