In order to support the new Workflow Foundation build technology used by Team Foundation Server 2010,  FinalBuilder 7 ships with a custom TFS Workflow activity and two XAML build templates. You can use these templates as-is to integrate FinalBuilder into your TFS build process, or you use them as a basis for creating your own custom build workflow.

Due to changes in the TFS API, builds created in TFS2008 with the FinalBuilder VS.NET TFS addin will not run under TFS2010.

This article will provide an overview of the FinalBuilder templates, give you a step-by-step guide to using one of them, and provide some introductory information on customisation. It assumes that you have already installed FinalBuilder 7 on your TFS Build Agent machine.

The FinalBuilder templates

There are two FinalBuilder templates provided, which are located in <FinalBuilderInstallDir>\TFS Templates

  • FinalBuilderBuild.xaml : replaces the build and test processes in the default TFS template with a call out to FinalBuilder. This template uses TFS to create the workspace, get the code out of source control (including the FinalBuilder project) and otherwise set up the Build Agent. It then calls FinalBuilder and runs the project you have specified. We'll step through how set up a build with this template in a minute.
  • FinalBuilderPostBuild.xaml : runs FinalBuilder at the end of the default TFS template. TFS is used to build and test the solution and the FinalBuilder project is run afterwards to do any post-build operations. It allows you to easily extend the TFS build with FinalBuilder, taking advantage of all of its built-in actions.

In both cases the output from FinalBuilder will appear in the TFS build log. If the FinalBuilder build fails, the TFS build will also fail. 

The rest of this article will cover:

Pages: 1 of 5 Next Page
Posted in: FinalBuilder
Actions: E-mail | Permalink |