were with the TFS 2010 many changes in the published functionality of the build management and customization shuffle mode.
The process uses a workflow-based Workflow Foundation 4.0 Engine to run builds. The build process is thus graphically customizable. There are 3 standard build process templates provided. DefaultTemplate.xaml for the normal build process. UpgradeTemplate.xaml to build process definitions created with Visual Studio 2005 or 2008. LabDefaultTemplate.xaml for builds that use the lab management.
The standard build process is quite simple and essentially involves four steps.
- Get the Build - Build Agent build environment - build environment
- Update Drop Location - build output directory
- Run on Agent Sources mark, start compile, automated tests and tasks to create
- Check In Gated Changes - If gated check-in, then check-in in the source code repository
customize the build process
To adjust the flow of process steps in the existing workflow, there are several possibilities.
- Drag'n drop existing standard activities from the toolbox .
- create their own activities by using own WF 4.0 Activities Library in XAML spelling.
- create their own activities through the use of its own activities WF 4.0 Library source code spelling.
In the following I would first like to address the adaptation of the "default templates".
First we open the Team Explorer Build the build definition, or create a new build definition. Then we look at the current set of process build definition file.
About New we can build a new definition file consists of creating a template.
This will of course put back in the source directory with the file name.
Now We can double-click the newly created build-process workflow template as desired even with the standard workflow activities change the TFS 2010 library.
save and build process by using the context menu start.
Finish.
In the next section, I demonstrate how to create and embed a custom workflow activity in the build-workflow.
0 comments:
Post a Comment