Triggering in Bamboo allows plan builds to be started automatically. Bamboo has the following trigger methods:
Trigger a build if code has changed:
Trigger a build based on a schedule:
Trigger a build depending on the outcome of other plans:
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:00 am and 10:00 am, and every 20 minutes between 1:00 pm and 10:00 pm".
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.
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.
See Repository polling.
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.
Bamboo will trigger scheduled builds of this plan based on a cron expression.
Single daily build
Bamboo will trigger a build of the plan once per day at a specified time.
See Single daily build.
|You can schedule Bamboo to run a build automatically whenever a selected tag appears in your repository. Tag triggering is enabled by default in Bamboo and becomes available when you link a repository to your Bamboo instance.
You can use tag triggering in Bamboo with the following repository types:
See Tag triggering.