ansaurus

Question

TFS 2008 getting all branches of source code while building one project

Answer 1

A:

Yes, the key is the line in your script:

Workspace="VMLSBUILD_17"

On the build computer, launch VS, click the "File" menu, and then choose "Source Control->Workspaces". Edit the workspace your script uses to only include the folders the build server needs. You can create multiple workspaces and choose which ones to use in your build scripts this way.

David Gladfelter 2010-02-18 14:56:53

David appreciate your response and it was very helpful in addressing our issue. Thanks again.

Bill 2010-02-19 15:53:05

This method is not recommended or supported.

Richard Berg 2010-02-19 17:23:35

Unless configured otherwise, Team Build will delete the workspace and recreate it using the folders specified in the build definition for every build. Changes made to the workspace by editing it manually on the build server will typically be lost on the next build.

Jason Stangroome 2010-09-22 14:23:11

Answer 2

+1 A:

Unlike in 2005, in TFS 2005 the workspace mappings used during the Get process is part of the actual build definition. Use the Build Explorer tool inside VS to edit the mappings to your liking. (Note: since you're primarily running VS2005, the 2008 Team Explorer client will appear as a standalone app.)

Richard Berg 2010-02-19 17:25:48

You're assuming that @Bill is using the TFS build definitions. I have a nightly build that I'm very happy with that uses powershell and MSBuild with the tfs command line tools. If the build feature of TFS had been useful to begin with, we might have gone down that route, but it's hard to justify re-visiting that effort.

David Gladfelter 2010-02-20 21:04:19

Of course I'm assuming that. Do you think it's coincidence that his buildlog.txt matches Team Build's?

Richard Berg 2010-02-20 22:44:27

ansaurus

tags:

views:

answers:

TFS 2008 getting all branches of source code while building one project

related questions