TFS 2017.3.1合并集合 [英] TFS 2017.3.1 Merge Collections
问题描述
我们当前正在TFS 2017.3.1 Prem上运行。我们有1个非常大的收藏，另外1个较小的收藏。我们想将较小的收藏移到较大的收藏。我们使用TFS中的所有内容，Git和源代码管理代码，工作项，构建，发行版...那里是否有任何工具/说明可用于执行此类操作。我看到有一个集成工具，但是不再支持它。还有一些工具会破坏我们对MS的支持。我的意思是，如果我们合并了馆藏，那么我们仍然可以从MS获得有关TFS问题的MSDN的帮助。
We are currently on TFS 2017.3.1 On Prem. We have 1 very large collection and another smaller collection. We would like to move the smaller collection into the larger. We use everything in TFS, code Git and Source Control, work items, builds, releases... Are there any tools/instructions out there for doing such a thing. I saw there was an integration tool, but it is no longer supported. Also of the tools out there is this something that would be break our support with MS. I mean if we merged collections would we still be able to get help from MS with our MSDN's for TFS issues. Is this something that is bound to cause us problems down the road if we do attempt it?
推荐答案
没有办法做到这一点吗？无需花费大量精力，也不会造成大量数据丢失（例如，工作项之间的链接很难迁移，工作项与提交之间的链接也很难迁移）。团队项目集合旨在完全隔离。
There's no way to do it without significant effort and some amount of data loss (links between work items, for example, are hard to migrate, as are links between work items and commits). Team Project Collections are intended to be completely isolated.
除非您直接操作TFS项目集合数据库，否则您不太可能遇到支持问题。使用已建立的API，一切都会好起来的。
Unless you're directly manipulating your TFS project collection databases, you're unlikely to have a support issue. Use the established APIs and you'll be fine.
老实说，我尝试过的所有工具都做得很好。没有人成功地构建出可以执行此操作的工具这一事实应该使您了解正确执行该操作的难度。
None of the tools I've tried do a great job, honestly. The fact that no one has successfully built a tool to do this should give you an idea of how hard it is to do properly.
我想说，您最好做以下事情：
I'd say you'd be better off doing the following:
- 将源 TPC设为只读。现在，它仅作为迁移之前工作项的参考。
- 移动Git存储库（克隆，新远程，推送）
- 移动仅活动的工作项和测试用例（手动或通过某些REST API脚本，具体取决于数量）
- 导出/导入构建和发布定义（再次手动或通过REST API脚本）。
- Make the "source" TPC read-only. It now exists only as a reference for work items from before the migration.
- Move your Git repos (clone, new remote, push)
- Move only active work items and test cases (manually or via some REST API scripting, depending on number)
- Export/import build and release definitions (again, manually or via REST API scripting).
这会很痛苦。
这篇关于TFS 2017.3.1合并集合的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
