This page last changed on May 06, 2007 by rosie@atlassian.com.
Triggering a build on code check-in has the advantage of placing minimal load on your Bamboo server, but requires that the repository is configured to fire an event to the Bamboo server.
 | Before you begin: If you choose to trigger a build on code check-in, you will need to configure your source-code repository to tell Bamboo whenever a code commit has occurred.
- For CVS, this is done by editing some files in the CVSROOT module.
- For Subversion, this is done by editing the Subversion respository's post-commit trigger file.
- Unfortunately, Perforce repository triggers are currently not supported by Bamboo.
You can access Bamboo's data from an external program by using Bamboo's REST-style remote API. You will first need to enable the remote API. |
To trigger a build on code check-in,
- Click 'Home' to go to the Dashboard.
- Click the 'All Plans' tab.
- Locate the plan in the list and click this icon:

- The 'Configuration' tab will be displayed. Click the 'Source Repository' sub-tab.
- In the 'Build Strategy' field, select 'Repository triggers the build when changes are committed' (see screenshot below).
- This will display the 'Trigger IP Address' field. If you want Bamboo to receive post-commit notifications from the respository's primary IP address, leave the 'Trigger IP Address' field blank. If you want Bamboo to receive post-commit notifications from a different IP address, type the IP address in the 'Trigger IP Address' field.
- Click the 'Save' button.
Screenshot: 'Plan Configuration--Source Repository-Build Strategy: Repository triggers the build when changes are committed'

RELATED TOPICS
Bamboo Documentation Home
|