This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

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.




To trigger a build on code check-in,

  1. Click 'Home' to go to the Dashboard.
  2. Click the 'All Plans' tab.
  3. Locate the plan in the list and click this icon:
  4. The 'Configuration' tab will be displayed. Click the 'Source Repository' sub-tab.
  5. In the 'Build Strategy' field, select 'Repository triggers the build when changes are committed' (see screenshot below).
  6. 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.
  7. Click the 'Save' button.









Screenshot: 'Plan Configuration--Source Repository-Build Strategy: Repository triggers the build when changes are committed'







 







RELATED TOPICS








Bamboo Documentation




  • No labels



Log a request with our support team.



Raise an issue for our developers.



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.