Geek Answers Handbook

Restore branch structure in original TFS management when only the most recent files are available

We migrated from another version control system. The last files from each branch were checked in folders in the original TFS 2010 control, and we used the "convert to branch" command to each folder of top-level branches. Starting with the initial checks, work on the chest and branches has been completed.

However, we cannot merge with the GUI because TFS does not understand the relationship between branches. The reparent command does not offer any parameters. Is there a way to use tf merge /baseless /discard /recursiveto establish relationships? Will this cause problems because after the initial checks were the checks carried out?

+5
source share
1 answer

I just spent the last 6 months moving 100 VSS repositories to TFS, so I feel your pain! I did this only in TFS 2008, but there is no reason why it should not work in 2010.

I would consider unreasonable merging as a last resort, since you will stick to command line sinks.

The trick is to establish the connection between the branches before importing the code.

(As an example, I use a simple branch of one dev, but you should be able to use the same theory, regardless of the number of branches)

  • , "", "dev" . .

  • "trunk" "dev" .

  • "trunk" "dev" , , TFS , , , . , ( , "dev" , , , , - , )

2 , , .

dev, , "trunk" "dev" , "dev" , , , ""

, ( 2) ​​ "" , ..

$/oldTeamProject/Devbranch $/NewTeamProject/DevBranch $/oldTeamProject/Trunk $/NewTeamProject/Trunk

$/NewTeamProject/Trunk $/NewTeamProject/DevBranch

TFS 2008, ( ). , "" , , . , , : -)

, TFS , , "dev" . , . , . , slike, , .

+10

More articles:


All Articles