AzureDevOpsPipelineProcessorOptions throws a serverPath null API exception for the build pipelines #970
Assignees
Comments
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days |
|
The project name would have to be mapped to the target one. Shouldn't be a Big Deal. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days |
|
I'll look into that the next weeks |
|
Hi @MrHinsh, @tomfrenzel any updates on this topic, I received the same error also with version 16.0.3. Used configuration: {
"MigrationTools": {
"Version": "16.0",
"Endpoints": {
"Source_AdoEndpoint": {
"EndpointType": "AzureDevOpsEndpoint",
"Organisation": "https://tfsurl.com/tfs/SourceCollection/",
"Project": "PROJECT",
"AuthenticationMode": "AccessToken",
"AccessToken": "MyToken",
"ReflectedWorkItemIdField": null,
"EndpointEnrichers": null
},
"Target_AdoEndpoint": {
"EndpointType": "AzureDevOpsEndpoint",
"Organisation": "https://tfsurl.com/tfs/TargetCollection/",
"Project": "PROJECT",
"AuthenticationMode": "AccessToken",
"AccessToken": "MyToken",
"ReflectedWorkItemIdField": null,
"EndpointEnrichers": null
}
},
"Processors": [
{
"ProcessorType": "AzureDevOpsPipelineProcessor",
"BuildPipelines": "",
"Enabled": "True",
"MigrateBuildPipelines": "True",
"MigrateReleasePipelines": "True",
"MigrateServiceConnections": "True",
"MigrateTaskGroups": "True",
"MigrateVariableGroups": "True",
"ReleasePipelines": "",
"RepositoryNameMaps": {
"PROJECT": "PROJECT"
},
"SourceName": "Source_AdoEndpoint",
"TargetName": "Target_AdoEndpoint"
}
]
}
}Error Message: POST https://tfsurl.com/tfs/TargetCollection//PROJECT/_apis/build/definitions/
{"$id":"1","innerException":null,"message":"Value cannot be null.\r\nParameter name: definition.Repository.Mappings.Mapping.ServerPath","typeName":"System.ArgumentNullException, mscorlib","typeKey":"ArgumentNullException","errorCode":0,"eventId":0}I need to add the [16.0.3] Error while running AzureDevOpsPipelineProcessor
System.NullReferenceException: Object reference not set to an instance of an object.
at MigrationTools.Processors.AzureDevOpsPipelineProcessor.MapRepositoriesInBuidDefinition(IEnumerable`1 sourceRepositories, IEnumerable`1 targetRepositories, BuildDefinition definitionToBeMigrated) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 386
at MigrationTools.Processors.AzureDevOpsPipelineProcessor.<CreateBuildPipelinesAsync>d__17.MoveNext() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 304
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at MigrationTools.Processors.AzureDevOpsPipelineProcessor.<MigratePipelinesAsync>d__9.MoveNext() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 86
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at MigrationTools.Processors.AzureDevOpsPipelineProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 40
at MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 98Kind Regards |
|
Having same issue config: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe your issue:
When running the pipelines processor with the default settings, an error similar to
Value cannot be null. Parameter name: definition.Repository.Mappings.Mapping.ServerPathappears. I just started using this tool and it seems to me that this processor is in some kind of alpha stage? Hopefully it isn't deprecated or anything.Source Details
Target Details
I'm using this tool to move a project from an organization to another one, so:
I have completed the following:
Simply running the tool with this default processor:
{ "$type": "AzureDevOpsPipelineProcessorOptions", "Enabled": true, "MigrateBuildPipelines": true, "MigrateReleasePipelines": true, "MigrateTaskGroups": true, "MigrateVariableGroups": true, "MigrateServiceConnections": true, "BuildPipelines": null, "ReleasePipelines": null, "ProcessorEnrichers": null, "SourceName": "Source", "TargetName": "Target" }Attempted fix
I noticed that in the
https://dev.azure.com/{org}/{proj}/_apis/build/definitions/{id}/URL we have this information:Then I took a look in the
BuildDefinitions.csfile and I noticed that the accessor for thetfvcMappingstring field is missing from thePropertiesclass (which is used in theRepositoryclass, which is used in theBuildDefinitionclass), so I created a derivedPropertiesBuildDefinitionclass (in case that its current form is still needed for some reason):This will simply write the server and local paths just like they were before, in the old project. This probably means that it may throw another exception if the project to migrate to has another name. I'm not creating a pull request for this reason and also because I'm not sure if this is fine for other Azure DevOps/TFS source versions.
The text was updated successfully, but these errors were encountered: