viernes, 13 de julio de 2012 21:22
I'm envisionning a migration according to the following needs :
- Migration from TFS2010 -> TFS2012 (new server)
- Change process template
- Keep WIT and source code history, but do not keep old WIT customizations.
So, my conclusion is that TFS integration is the only way.
--- 1. Could you confirm ?
I made a quick test with TFS integration on a dummy project. (SC and WIT at the same time)
Everything is well migrated excepted the association changeset / WIT.
Seen in the history of the migrated WIT :
Resolved with changeset 106: Here a comment
(TFS Integration from 'vsalm (WIT)' Id: 46 (rev 2);)
... where 106 is the # of the original changeset and 46 is the # of the original WIT..
--- 2. Any idea ?
Todas las respuestas
martes, 17 de julio de 2012 7:21Moderador
Thanks for your post!
Do you mean you use TFS Integration Platform to migrate from TFS 2010 to TFS 2012?
To migrate the sources code and WIT, TFS Integration Platform is supposed to do the work. It migrates the changeset history as well. Can you post the related errors here?
About "Change process template", you can refer to http://social.msdn.microsoft.com/Forums/EU/tfsprocess/thread/d380ce47-beee-488f-9ecc-dfc3de71d0cb
Hope it helps!
Cathy Kong [MSFT]
MSDN Community Support | Feedback to us
- Marcado como respuesta Cathy KongMicrosoft Contingent Staff, Moderator lunes, 23 de julio de 2012 7:35
lunes, 06 de agosto de 2012 8:16
>> Do you mean you use TFS Integration Platform to migrate from TFS 2010 to TFS 2012?
Yes, this is what I meant.
>> About "Change process template", you can refer to http://social.msdn.microsoft.com/Forums/EU/tfsprocess/thread/d380ce47-beee-488f-9ecc-dfc3de71d0cb
I'm not very confortable with this solution.
I would prefer an 'official' way, like using TFS Integration or 'upgrade scenario' in TFS 2012 new hardware installation.