Clearcase -> TFS 2010 migration "flattens" cc branches into linear sequence in TFS, any way to migrate selected branches?

Answered Clearcase -> TFS 2010 migration "flattens" cc branches into linear sequence in TFS, any way to migrate selected branches?

  • Wednesday, April 25, 2012 1:42 PM
     
     

    Hi

    I recently migrated some source files from a clearcase 7.1 vob into a TFS 2010 project using the full history option. I was initially told that the source in clearcase was only on the main branch, and my cc view was set to the default of /main/LATEST.

    After the migration was completed I was told there were actually a small number of files with a versions on this branch (which is branched directly off the main branch). Cross checking with the versions migrated to TFS I can see that the versions on the sub-branch in clearcase were branched off /main/LATEST and have been migrated as the last few versions into the TFS history

    i.e

    Path/version in clearcase                       Path and changeset in TFS 

    \vob\path\file@@\main\LATEST              $/TP/path/file changeset 10
    \vob\path\file@@\main\branch\1           $/TP/path/file changeset 11
    \vob\path\file@@\main\branch\2           $/TP/path/file changeset 12

    I can sort of see why versions on branches not visible in the view have been migrated as it was a full history migration (I can see from the execution of the migration that it runs a cleartool lshistory which includes the branched versions). I know TFS does branching differently and it doesn't map in the same way however it has lost some of the structure by flattenning out what was on the branch and what was on main into one single list of versions in the history.

    It would be a useful enhancement to be able to filter the migration to say "just migrate this branch/branches" with their history rather than just filter out file/folders in the filter pairs. Or is there a way to do it already?

    Best wishes

    Reg

All Replies