如何在同一VSTS帐户中迁移具有历史记录的团队项目? [英] How to migrate team project with history within same VSTS account?

查看:91
本文介绍了如何在同一VSTS帐户中迁移具有历史记录的团队项目?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们需要迁移VSTS团队项目.我已经从 VSTS复制项目

  • VSTS同步迁移者
  • OpsHub
  • 解决方案

    目前尚不清楚您要从哪里迁移什么.以及为什么您将无法访问现有项目.根据您选择的当前源控件类型,您有不同的选项.

    您可以尝试的一个方法是创建2个新帐户,并使整个旧帐户保持只读状态.这应该使每个人都可以使用历史记录.然后,您可以仅使用最新版本的资源来增加任意数量的新帐户.

    Git

    如果它是一个Git仓库,那么它就像创建整个仓库的本地副本一样简单,在VSTS中创建一个新的团队项目并将该副本推入它的第二个家中.

    TFVC

    如果是TFVC,则要困难得多.过去我使用过OpsHub,效果很好,但在我们这种情况下,完全陷入了一些奇怪的合并情况.这些可能是在TFS 2008中主持该团队项目时所做的工作的一部分,因此您可能会比我们幸运.

    您可以决定迁移到Git作为迁移的一部分.使用 git-tfs创建本地git存储库包含所有TFVC历史记录,然后将其推送到新团队项目中的裸Git存储库中.或使用TFVC导入工具. 有关此主题的文档很多../p>

    据我所知,VSTS Sync Migrator支持无历史记录的快照.哪个不适合您.

    VSTS复制项目不支持TFVC,在这种情况下,该选项是不可选的.

    列表中缺少的一个选项是及时迁移,它支持从TFVC到TFVC的迁移.我很久以前就使用它们在TFS服务器之间复制数据.当时他们的工作完全符合广告宣传.

    We need to migrate our VSTS team project. I already saw that this is an eagerly awaited feature from the Visual Studio user Voice.

    However, in our case the new team project is to be in the same VSTS account. Is there a way to do this while also keeping version control change history? Keeping the change history available as part of the old team project is unfortunately not an option as we will lose access to the old team project soon after migration.

    If somebody has done this before with the help of any of the below tools, then it would be great if they can share their experience:

    解决方案

    It's a bit unclear what you're about to migrate from where. And why you'd lose access to the existing project. And you have different options based on the current source control type selected.

    One option which you could try is to create 2 new accounts and leave the whole old account in read-only state. That should leave the history available to everyone. You can then spin up as many new accounts as you want, using just the latest version of the sources.

    Git

    If it's a Git repository it's as simple as making a local clone of the whole repo, creating a new team project in VSTS and pushing the clone into its second home.

    TFVC

    If it's TFVC, it's much harder. I've used OpsHub in the past which works reasonably well, but in our case completely got stuck in a couple of strange merge situations. Those were probably created as part of work done back when that team project was hosted in TFS 2008, so you may be luckier than we were.

    You could decide to move to Git as part of your migration. Use git-tfs to create a local git repository with all your TFVC history and then push that into a bare Git repository in your new team project. Or use the TFVC import tool. There's quite a bit of documentation on this subject.

    The VSTS Sync Migrator supports a snapshot without history as far as I can tell. Which would not suit you.

    VSTS Copy Project doesn't support TFVC, and is no option in this case.

    An option that's missing from your list is Timely Migration, it supports TFVC to TFVC migrations among other options. I've used them a long time ago to copy data between TFS servers. Back then they were working exactly as advertised.

    这篇关于如何在同一VSTS帐户中迁移具有历史记录的团队项目?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

    查看全文
    登录 关闭
    扫码关注1秒登录
    发送“验证码”获取 | 15天全站免登陆