New Team Project from Existing, Branched Project - How to Retain Branch Paths?

Question

I have an existing Team Project created with the out of the box MSF for Agile 5.0 process template. We have since standardized on a customized Microsoft Scrum 1.0 template. I have just created a new Team Project, using our current template, based on the existing project. No further work will be done in the original Team Project.

This existing Team Project uses the "Basic" branch pattern from the ALM Ranger's Branching Guidance:

Original Team Project Branch Hierarchy

When creating the new project, I took the option to start the new project by branching from the original. The result is not what I had in mind:

New Team Project Branch Hierarchy

I wanted a "Team Project 2/Development/Development" branch that branches from the "Team Project 2/Main", and the same with "Release". This leaves me two questions:

Is there something I should have done differently to get the structure I want?
Is there something I can do now to change the new (bad) structure to the one that I want?

So you really wanted TP1\Main -> TP2\Main ->TP2\development & TP2\Release? — Nick Nieslanik, Oct 20 '11 at 14:52
Yes, that's right. I wanted the same structure in the new project as in the old. In fact, I didn't really want to create a new branch, but I was forced to do so. — John Saunders, Oct 20 '11 at 15:56

score 2 · Accepted Answer · edited Oct 20 '11 at 17:16

To get the structure you wanted, I think you would have needed to do the following:

Create the new Team Project with an empty source control area rather than branching.
Then in TP1, branch Main to TP2/Main (or "staging" and then into main ) manually
Then create the branches for Development/Dev and Release/Release off the new Main

What this doesn't do is migrate your old Dev and release branches. To get any changes from them over to your new structure, you'd have to preface this entire process with merges back into the TP1\Main. Obviously this is a little less than ideal if you want to keep the old "Release" frozen. In that case you'd probably want to Branch that explicitly into the new TP2/Release/Release area and note that it came from the old project. Then you could establish the new branch relationship to TP2/Main on newer releases only.

As for "Is there anything I can do now?" I think the answer is, no, nothing short of something very drastic, like starting this process over again or just shutting down the existing branches and re-branching using the suggestions above.

I don't see an option to not create source control. The options are either new folder or else choose a branch. — John Saunders, Oct 20 '11 at 16:43
@JohnSaunders By empty source control, I meant a new folder. Then just lay everything underneath that... — Nick Nieslanik, Oct 20 '11 at 17:12

Bruno Matuk · Answer 2 · 2012-04-27T02:42:00.537

To achive the structure you want, after create the new Team Project, you have to perform a Baseless Merge. Baseless merge is used to merge branches that don´t have relationship. After you perform a baselees merge, Tfs will establishe a relationship between the branches.

Note: In the "View Hierarchy" window you won´t be able to see the connection link between the branches, but througth the "Source Control Merge Wizard", you will be able to select the branch and merge.

In your case, you can perform a baselees merge between "xxx2/Main" and "xxx2/Developement/Developement" and another one between "xxx2/Main" and "xxx2/Release/Release". After performing the baseless merge, TFS will create the relationship between the branches, and you´ll get your structure.

Edit 1: "Source Control Merge Wizard" == In "Source Control Explorer" > Right Click the desired branch > Banching and Merging > Merge. In the "Target branch" you will be able to select the branch.

Thanks for the info. Can you give me a link about the "Source Control Merge Wizard"? — John Saunders, Apr 26 '12 at 16:55

New Team Project from Existing, Branched Project - How to Retain Branch Paths?

2 Answers2