This page last changed on Oct 16, 2008 by alui.
There are a variety of ways in which a build can be triggered for a plan:
- Code updated — a build can be triggered whenever one or more authors checks-in code.
- Scheduled build — a build can be scheduled to occur at regular intervals.
- Dependency — a build can be triggered whenever a successful build occurs for another plan.
- Manual build — a build can be triggered manually.
- Initial clean build — a build will be triggered when a new plan is created.
The way in which each build was triggered is listed in the 'Reason' column on the Dashboard.
 | Considerations for choosing a Build Strategy
- Code 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:
- Scheduled build:
Triggering a build on schedule can allow a team to structure the day according to a predictable schedule. Note that scheduled builds are run regardless of whether or not any code changes have occurred. There are two ways to schedule a build:
- Single Daily Build —
A single daily build runs at a time of your choice. This is particularly suitable for builds that take a long time to complete. See Scheduling a Single Daily Build.
- Cron-Based Scheduling —
A cron-based schedule allows you to schedule builds according to a flexible cron expression. For example, "0 0/30 9-19 ? * MON-FRI" would trigger a build every half-an-hour from 9am to 7pm, Monday to Friday. See Specifying a Cron-based Schedule.
|
Also see Stopping an Active Build.
|