This project has moved and is read-only. For the latest updates, please go here.

Confusing language in Scenarios document: build scripts

Apr 13, 2010 at 11:07 PM
Edited Apr 13, 2010 at 11:07 PM


I have a question about some confusing language in the TFS_Branching_Guide_Scenarios_2010_v1.pdf document at the top of page 23:

"Team build scripts (i.e. TeamBuildTypes) should be considered first-class artifact that should be isolated from all other branches in the source explorer tree. It should be isolated from the actual source code, preferably in a directory that is a sibling of the "source" directory of a given branch. For example, in the Main branch, you should have both $/WoodGroveBanking/Main/source and $/WoodGroveBanking/Main/build. As branches are forked off of main, the build scripts will travel alongside with the source code at the same relative path ensuring stability of builds regardless of the branch."

The first sentence makes it sound like the TeamBuildTypes folder should live outside of all of your branches, perhaps at the root level of the team project (as it had to in TFS05). However, the rest of the paragraph seems to indicate that TeamBuildTypes should live inside your branch so that the scripts get branched along with everything else. This way, you could create new build definitions per-branch based on those branched scripts (so you could have an automated build for each dev branch, the main branch, each release branch, etc.)

Can you clarify the language here? It sounds like having TeamBuildTypes live within your main branch is the way to go, but I wanted to be sure.