Geeks With Blogs
I [heart] code! .NET musings from the chick side

If you have a large code base, you can optimize your build time for Integration Builds by building only the class libraries that have changed since the last build.

This is done by editing the build project file for your incremental builds.

1. Locate your build project file in Team Foundation Version Control:

<Server Name> - <Project Name> - TeamBuildTypes - <Build Definition Name> - TFSBuild.proj

 

2. Add the following lines to the end:

 

<PropertyGroup>     
<SkipClean>true</SkipClean>     
<SkipInitializeWorkspace>true</SkipInitializeWorkspace>     
 <ForceGet>false</ForceGet> 
</PropertyGroup> 

 

 

SkipClean: When true, skips the clean of a solution before building it.

SkipInitializeWorkspace: When true, skips the deletion and recreation of the workspace

ForceGet: Gets all files from source control regardless of status. Set to false to retrieve only the changed files.

 

If you are doing incremental builds for your continuous integration builds, it is good practice to have another build definition that rebuilds your entire solution run for the Daily Build.

Posted on Tuesday, May 27, 2008 1:31 PM | Back to top


Comments on this post: Incremental Builds in Team Foundation Server

# re: Incremental Builds in Team Foundation Server
Requesting Gravatar...
Thanks for the pointers! If we are doing incremental build, can the version number be made to remain same as the past build?
Left by Kathir on Dec 28, 2012 9:42 AM

Your comment:
 (will show your gravatar)


Copyright © Kirstin Juhl | Powered by: GeeksWithBlogs.net