从 Devops Server 迁移到 Devops Services 的验证错误

Question

我正在测试将项目从本地 DevOps 服务器（最新 2019 更新 1.1）迁移到 DevOps 服务。我正在使用最新的 DataMigrationTool (Migrate.exe)，但结果非常奇怪。

我正在使用

Migrator.exe validate /collection:http://localhost:8080/tfs/MyCollection /saveprocesses

问题包括：

1. 使用未修改流程的项目，例如香草 Scrum 不匹配。例如：

[Info   @14:59:27.587] === Found 220 error(s) when compared against process TFS 2019 RTM Scrum ===
[Error  @14:59:27.587] Rules for field 'Microsoft.VSTS.Common.Priority' do not match at level 'Task'.
[Error  @14:59:27.587] Rules for field 'Microsoft.VSTS.Common.Activity' do not match at level 'Task'.
[Error  @14:59:27.587] Rules for field 'Microsoft.VSTS.Build.IntegrationBuild' do not match at level 'Task'.
[Error  @14:59:27.587] Rules for field 'Microsoft.VSTS.CMMI.Blocked' do not match at level 'Task'.
[Error  @14:59:27.587] Custom type 'Task' added a new field 'Microsoft.VSTS.Common.ActivatedDate'.
[Error  @14:59:27.587] Custom type 'Task' added a new field 'Microsoft.VSTS.Common.ActivatedBy'.
[Error  @14:59:27.587] Custom type 'Task' added rules for field 'System.Reason' at level 'transition[To Do->In Progress]'.
[Error  @14:59:27.587] Custom type 'Task' added rules for field 'System.Reason' at level 'transition[In Progress->Done]'.
[Error  @14:59:27.587] Custom type 'Task' added rules for field 'System.Reason' at level 'transition[To Do->Done]'.
[Error  @14:59:27.587] Custom type 'Task' added rules for field 'System.Reason' at level 'transition[->To Do]'.

文档说未修改的进程应该匹配没有错误。这些错误是什么意思？

1. 导出的流程 xml 不符合架构，即使对于使用 未修改 流程的项目（在其他项目具有修改/继承流程的集合中），也会出现数百个验证错误。

例子：

  <FIELD name="Severity" refname="Microsoft.VSTS.Common.Severity" type="String" reportable="dimension">
     <ALLOWEXISTINGVALUE />
     <ALLOWEDVALUES expanditems="true" />
     <DEFAULT from="value" value="3 - Medium" />
     <ALLOWEDVALUES expanditems="true" />
  </FIELD>

这里重复了 allowedvalues 标记，并且（如果我正确理解架构）不能为空但需要指定 GLOBALLIST 或 LISTITEM 子级。

[Error  @13:39:09.158] Step : ProcessValidation - Failure Type - Validation failed : Invalid process template: WorkItem Tracking\TypeDefinitions\Task.xml:158: TF402594: File violates the schema with the following error: The element 'ALLOWEDVALUES' has incomplete content. List of possible elements expected: 'GLOBALLIST, LISTITEM'.
[Error  @13:39:09.158] Step : ProcessValidation - Failure Type - Validation failed : Invalid process template: WorkItem Tracking\TypeDefinitions\Task.xml:167: TF402594: File violates the schema with the following error: The element 'ALLOWEDVALUES' has incomplete content. List of possible elements expected: 'GLOBALLIST, LISTITEM'.
[Error  @13:39:09.158] Step : ProcessValidation - Failure Type - Validation failed : Invalid process template: WorkItem Tracking\TypeDefinitions\Task.xml:172: TF402594: File violates the schema with the following error: The element 'ALLOWEDVALUES' has incomplete content. List of possible elements expected: 'GLOBALLIST, LISTITEM'.
[Error  @13:39:09.158] Step : ProcessValidation - Failure Type - Validation failed : Invalid process template: WorkItem Tracking\TypeDefinitions\Task.xml:203: TF402594: File violates the schema with the following error: The element 'ALLOWEDVALUES' has incomplete content. List of possible elements expected: 'GLOBALLIST, LISTITEM'.
[Error  @13:39:09.158] Step : ProcessValidation - Failure Type - Validation failed : Invalid process template: WorkItem Tracking\TypeDefinitions\Task.xml:215: TF402594: File violates the schema with the following error: The element 'ALLOWEDVALUES' has incomplete content. List of possible elements expected: 'GLOBALLIST, LISTITEM'.
[Error  @13:39:09.158] Step : ProcessValidation - Failure Type - Validation failed : Invalid process template: WorkItem Tracking\TypeDefinitions\Task.xml:243: TF402594: File violates the schema with the following error: The element 'ALLOWEDVALUES' has incomplete content. List of possible elements expected: 'GLOBALLIST, LISTITEM'.

1. 使用修改过的流程（继承自 Scrum）对项目进行验证，其中某些工作项类型具有新状态，存在未修改流程的所有错误以及其他架构违规。例如：

<TRANSITION from="X" to="Resolved">
   <REASONS>
      <DEFAULTREASON value="Moved out of state X" />
      <DEFAULTREASON value="Moved to state Resolved " />
   </REASONS>
</TRANSITION>

<REASONS> 只能有一个<DEFAULTREASON> 标签。 继承过程中的状态就是这种情况。如果必须“修复”这些错误才能迁移项目，我该怎么做？ DevOps Server 2019 的继承过程模型中的状态和转换在哪里编辑？

如果我实际上无法修复它们，那么这些错误表明什么？工具有问题吗？我该如何解决它们？

Answer 1

我已经用 17.153.29522.3 (AzureDevOps2019.Update1.1) 测试了 migration tool，它按预期工作。

您的任务工作项似乎已自定义并出现错误，您需要先解决错误。如果你有其他的集合，你可以和他们一起处理验证，看看你是否可以成功验证。