3.2 Triggering a Build when Code is Updated

Triggering a build when code is updated ensures that a build only occurs when necessary. There are two ways to trigger a build when code is updated:

• "Pull strategy" —
  Polling the repository for code changes means that Bamboo will check-out the source-code on a regular basis, and examine it for changes. If Bamboo detects a change, it will trigger a build. See 3.2.1 Polling the Repository for Code Changes.
• "Push strategy" —
  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. See 3.2.2 Triggering a Build on Code Check-in.

RELATED TOPICS

• 3.1 About Build Triggering
• 3.2 Triggering a Build when Code is Updated
  • 3.2.1 Polling the Repository for Code Changes
  • 3.2.2 Triggering a Build on Code Check-in
• 3.3 Triggering a Build on Schedule
  • 3.3.1 Scheduling a Single Daily Build
  • 3.3.2 Specifying a Cron-based Schedule
• 3.4 Triggering a Build when another Build finishes
• 3.5 Triggering a Build Manually