通过OpsHub进行TFS迁移-非常慢 [英] TFS migration via OpsHub - very slow

查看:99
本文介绍了通过OpsHub进行TFS迁移-非常慢的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在测试通过OpsHub(1.1.0.005)将TFS2013(仅限源代码控制)迁移到VSO.

I am testing a TFS2013 (source control only) migration to VSO via OpsHub (1.1.0.005).

我选择了一个具有2500个变更集的团队项目,但是在迁移时,OpsHub UI会显示[迭代值]/32894变更集/已传递的标签.

I chose a Team Project that has 2500 changesets, but when migrating, the OpsHub UI displays [iterating value]/32894 Changeset(s)/Labels passed.

我没有看过有多少标签,但是我怀疑是否有30,000 +.

I have not looked to see how many labels exist, but I doubt there are 30,000+.

迁移过程已经运行了5个小时,看起来可能已经运行了3或4天.

The migration process has been running for 5 hours, and looks like it may run for 3 or 4 days.

迁移小型团队项目真的需要多长时间?

Is this really how long it takes to migrate a small Team Project?

推荐答案

"30k"标签将是收集级别"范围内的标签.此后,该实用程序将迁移TFS构建标签(TFS构建标签在TFS构建时在集合级别范围内自动创建).但是,与已选择要迁移的项目无关的标签将不会被迁移.但是,必须对它们进行预处理,以决定它们是否属于相关项目.

The 30k Labels would be those that exist at the Collection Level scope. Since, the utility migrates TFS Build Labels (which TFS automatically creates at the collection level scope). However, the labels which are not pertaining to the project(s) that have been selected to be migrated will NOT be migrated. Yet they will have to be preprocessed to decide if they are of the relevant project or not.

因此,您将看到总计数为合计,但仅对相关标签进行处理和迁移.并且不需要标签的迭代将在几秒钟内完成.

Hence you will see the total count as an aggregation, but the processing+migration will only be done for relevant labels. And the iteration over unneeded labels will be done with in seconds.

附带说明,正在迁移的项目的大致规模是什么?

On a side note, what is the rough size of the project that is being migrated?

这篇关于通过OpsHub进行TFS迁移-非常慢的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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