管道迁移是否有效 - 一直在使用它并收到错误 There is no endpoint named that or duplicates of the same name
Do Pipeline Migrations work - been using it and getting the error There is no endpoint named that or duplicates of the same name
一直在评估该工具,效果很好
只有一个问题 - 管道迁移是否在 prem 上使用 azure devops 工作,并且在我们看来我不知道如何配置它们
报告
[17:51:53 ERR] 未处理的异常!
System.InvalidOperationException: 没有名为那个的端点或同名的重复端点
在 D:\a\s\src\MigrationTools\Endpoints\EndpointFactory.cs:line 49 中的 MigrationTools.Endpoints.EndpointFactory.CreateEndpoint(字符串名称)
在 MigrationTools.Processors.Processor.Configure(IProcessorOptions 选项)在 D:\a\s\src\MigrationTools\Processors\Processor.cs:line 50
在 MigrationTools.Processors.AzureDevOpsPipelineProcessor.Configure(IProcessorOptions 选项)在 D:\a\s\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:第 37 行
在 D:\a\s\src\MigrationTools_EngineV1\Containers\ProcessorContainer.cs:line 61 中的 MigrationTools._EngineV1.Containers.ProcessorContainer.Configure()
在 MigrationTools.MigrationEngine.Run() 中 D:\a\s\src\MigrationTools\MigrationEngine.cs: 第 87 行
在 MigrationTools.Host.ExecuteHostedService.b__5_1() 中 D:\a\s\src\MigrationTools.Host\ExecuteHostedService.cs: 第 38 行
[17:51:53 INF] 应用程序正在关闭...
{
"$type": "AzureDevOpsPipelineProcessorOptions",
"Enabled": true,
"MigrateBuildPipelines": true,
"MigrateReleasePipelines": true,
"MigrateTaskGroups": true,
"MigrateVariableGroups": true,
"MigrateServiceConnections": false,
"BuildPipelines": null,
"ReleasePipelines": null,
"RefName": null,
"SourceName": "xxxxxxxxxxx",
"TargetName": "xxxxxxxxxxx"
}
您必须创建两个“端点”,以便管道处理器知道要使用哪个。如果你在这里查看源代码,你没有任何东西作为参数:
MigrationTools.Endpoints.EndpointFactory.CreateEndpoint(字符串名称)
https://github.com/nkdAgility/azure-devops-migration-tools/blob/master/src/MigrationTools/Endpoints/EndpointFactory.cs
我在使用团队设置处理器时遇到了同样的问题。这个 link 确实帮助我创建了端点 https://github.com/nkdAgility/azure-devops-migration-tools/pull/860/files
在下面的团队设置处理器选项示例中,您的 SourceName 将是 TfsTeamSettingsSource,而您的 TargetName 将是 TfsTeamSettingsTarget。我必须阅读源代码才能弄清楚,AccessToken 的“身份验证模式”是 0;它不会接受字符串 "AccessToken" :|.
请参阅下面的团队设置处理器选项示例:
**Endpoints**": {
"TfsTeamSettingsEndpoints": [
{
"Name": "**TeamSettingsSource**",
"AccessToken": "",
"Query": {
"Query": "SELECT [System.Id], [System.Tags] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan') ORDER BY [System.ChangedDate] desc"
},
"Organisation": "https://dev.azure.com/like10-demos/",
"Project": "SourceProject",
"ReflectedWorkItemIdField": "ReflectedWorkItemId",
"AuthenticationMode": "Prompt",
"AllowCrossProjectLinking": false,
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
{
"Name": "**TeamSettingsTarget**",
"AccessToken": "",
"Query": {
"Query": "SELECT [System.Id], [System.Tags] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan') ORDER BY [System.ChangedDate] desc"
},
"Organisation": "https://dev.azure.com/like10-demos/",
"Project": "TargetProject",
"ReflectedWorkItemIdField": "ReflectedWorkItemId",
"AuthenticationMode": "Prompt",
"AllowCrossProjectLinking": false,
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
}
]
},
一直在评估该工具,效果很好
只有一个问题 - 管道迁移是否在 prem 上使用 azure devops 工作,并且在我们看来我不知道如何配置它们
报告
[17:51:53 ERR] 未处理的异常! System.InvalidOperationException: 没有名为那个的端点或同名的重复端点 在 D:\a\s\src\MigrationTools\Endpoints\EndpointFactory.cs:line 49 中的 MigrationTools.Endpoints.EndpointFactory.CreateEndpoint(字符串名称) 在 MigrationTools.Processors.Processor.Configure(IProcessorOptions 选项)在 D:\a\s\src\MigrationTools\Processors\Processor.cs:line 50 在 MigrationTools.Processors.AzureDevOpsPipelineProcessor.Configure(IProcessorOptions 选项)在 D:\a\s\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:第 37 行 在 D:\a\s\src\MigrationTools_EngineV1\Containers\ProcessorContainer.cs:line 61 中的 MigrationTools._EngineV1.Containers.ProcessorContainer.Configure() 在 MigrationTools.MigrationEngine.Run() 中 D:\a\s\src\MigrationTools\MigrationEngine.cs: 第 87 行 在 MigrationTools.Host.ExecuteHostedService.b__5_1() 中 D:\a\s\src\MigrationTools.Host\ExecuteHostedService.cs: 第 38 行 [17:51:53 INF] 应用程序正在关闭...
{
"$type": "AzureDevOpsPipelineProcessorOptions",
"Enabled": true,
"MigrateBuildPipelines": true,
"MigrateReleasePipelines": true,
"MigrateTaskGroups": true,
"MigrateVariableGroups": true,
"MigrateServiceConnections": false,
"BuildPipelines": null,
"ReleasePipelines": null,
"RefName": null,
"SourceName": "xxxxxxxxxxx",
"TargetName": "xxxxxxxxxxx"
}
您必须创建两个“端点”,以便管道处理器知道要使用哪个。如果你在这里查看源代码,你没有任何东西作为参数:
MigrationTools.Endpoints.EndpointFactory.CreateEndpoint(字符串名称) https://github.com/nkdAgility/azure-devops-migration-tools/blob/master/src/MigrationTools/Endpoints/EndpointFactory.cs
我在使用团队设置处理器时遇到了同样的问题。这个 link 确实帮助我创建了端点 https://github.com/nkdAgility/azure-devops-migration-tools/pull/860/files
在下面的团队设置处理器选项示例中,您的 SourceName 将是 TfsTeamSettingsSource,而您的 TargetName 将是 TfsTeamSettingsTarget。我必须阅读源代码才能弄清楚,AccessToken 的“身份验证模式”是 0;它不会接受字符串 "AccessToken" :|.
请参阅下面的团队设置处理器选项示例:
**Endpoints**": {
"TfsTeamSettingsEndpoints": [
{
"Name": "**TeamSettingsSource**",
"AccessToken": "",
"Query": {
"Query": "SELECT [System.Id], [System.Tags] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan') ORDER BY [System.ChangedDate] desc"
},
"Organisation": "https://dev.azure.com/like10-demos/",
"Project": "SourceProject",
"ReflectedWorkItemIdField": "ReflectedWorkItemId",
"AuthenticationMode": "Prompt",
"AllowCrossProjectLinking": false,
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
{
"Name": "**TeamSettingsTarget**",
"AccessToken": "",
"Query": {
"Query": "SELECT [System.Id], [System.Tags] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan') ORDER BY [System.ChangedDate] desc"
},
"Organisation": "https://dev.azure.com/like10-demos/",
"Project": "TargetProject",
"ReflectedWorkItemIdField": "ReflectedWorkItemId",
"AuthenticationMode": "Prompt",
"AllowCrossProjectLinking": false,
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
}
]
},