Triggering a build manually or by build dependencies allows you to ensure that builds are only triggered manually or by parent builds of dependent builds. You can also trigger builds based on code changes or based on a schedule, rather than triggering builds manually. On this page:

Starting a Plan Build Manually

To start a Plan build manually:

1. Click 'Home' to go to the Dashboard.
2. Locate the relevant Plan and click the 'Checkout & Build' icon

Configuring a Plan's Build to be Triggered Only Manually or via a Dependency

You can specify that a plan should only ever be built manually or triggered by other builds. This is useful for:

• Broken builds — If a build is broken, you may want to temporarily specify 'Manual & dependent builds only'. This means that a failing build will not be triggered frequently and hence will not take up time and processing power when other builds could be running.
• Dependent builds —

  If you specify that a build should run when another build successfully finishes, you may want to prevent it from running at other times. You can achieve this by specifying 'Manual & dependent builds only'.

To allow a Plan's build to be triggered only manually or via a dependency:

1. Click 'Home' to go to the Dashboard.
2. Click the 'All Plans' tab.
3. Locate the plan in the list and click the 'Edit' icon to display the Plan's Configuration pages.
4. Click the 'Repository' tab.
5. In the 'Build Strategy' field, select 'Manual & dependent builds only' (see screenshot below).
6. 「保存」ボタンをクリックします。

Screenshot above: Plan Configuration — Build Strategy: Manual builds only

注意

関連トピック

Stopping an Active Build