How to: Configure the Builds Check-in Policy for Continuous Builds

You can configure Team Foundation Build to run continuous builds. For more information, see How to: Run Continuous Builds. When you use continuous integration to trigger builds, every check-in starts a build. If one or more previously checked-in files cause a build break, the Builds policy displays a check-in policy error message when you try to check in a new file. The error message includes the build definition name and the user whose check-in triggered the build. The Builds policy notifies you of build breaks before you can add more files to the build. This allows you to deal with build-related problems immediately.

Required Permissions

To complete this procedure, you must have the Manipulate security settings permission set to Allow. For more information, see Team Foundation Server Permissions.

To configure the Builds policy

  1. In Team Explorer, right-click your team project, click Team Project Settings, and then click Source Control.

    The Source Control Settings dialog box appears.

  2. Click the Check-in Policy tab and then click Add.

    The Add Check-in Policy dialog box appears.

  3. In the Check-in Policy list box, select Builds, and click OK.

  4. On the Source Control Settings dialog bog, click OK.

    The Builds check-in policy is now in effect for your team project for future check-ins. If the Builds policy detects a broken continuous integration build, the system displays an error message:

    The last build of definition <build definition name>, triggered by user <user name>, failed.

See Also

Tasks

Walkthrough: Customizing Check-In Policies and Notes

How to: Create a Build Definition

Concepts

Working with Check-In Policies and Notes