This is the second part of the Team Foundation Build series that I started back in October.á One of the important things to understand about Team Build is the build process.á As I outlined in the first part of this series, Team Build is nothing more than a set of custom tasks for MS Build.á The custom tasks are called from a set of custom targets that are organized to complete the build.?
Here are the targets and the order in which they are called:
-
CheckSettingsForEndToEndIteration
-
EndToEndIteration
-
BeforeEndToEndIteration
-
BuildNumberOverrideTarget
-
InitializeEndToEndIteration
-
Clean
-
BeforeClean
-
CoreClean
-
AfterClean
-
TeamBuild
-
InitializeBuild
-
PreBuild
-
InitializeWorkspace
-
BeforeGet
-
CoreGet
-
AfterGet
-
BeforeLabel
-
CoreLabel
-
AfterLabel
-
Compile
-
BeforeCompile
-
CoreCompile
-
AfterCompile
-
PostBuild
-
GetChangeSetsAndUpdateWorkItems
-
Test
-
BeforeTest
-
CoreTest
-
RunTestWithConfiguration
-
AfterTest
-
PackageBinaries
-
DropBuild
-
BeforeDropBuild
-
CoreDropBuild
-
CopyLogFiles
-
AfterDropBuild
-
AfterEndToEndIteration
Errors that occur during the build are handled by these targets:
While you can override any of the targets listed above Team Build has several targets that are setup to be overridden out of the box.á Those targets are:
Next we will look at the process in more detail and drill into how Team Build does what it does.
Happy Coding!