[Bug]: IEnumerable1 sourceRepositories, IEnumerable1 targetRepositories, BuildDefinition definitionToBeMigrated

[tiwarishrijan]

Version

• I confirm that I am using the latest version

Source Version

Azure DevOps Service

Target Version

Azure DevOps Service

Relevant configuration

## Processor 
{
        "ProcessorType": "AzureDevOpsPipelineProcessor",
        "Enabled": true,
        "MigrateBuildPipelines": true,
        "MigrateReleasePipelines": true,
        "MigrateServiceConnections": true,
        "MigrateTaskGroups": true,
        "MigrateVariableGroups": true,
        "RepositoryNameMaps": {},
        "SourceName": "AzureDevOpsEndpointSource",
        "TargetName": "AzureDevOpsEndpointTarget"
}

## Endpoint
{
        "EndpointType": "AzureDevOpsEndpoint",
        "AuthenticationMode": "AccessToken",
        "AccessToken": "***",
        "Organisation": "__ORGANIZATION_URL__",
        "Project": "__PROJECT_NAME__",
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId"
}

Relevant log output

[13:48:43 FTL] [16.0.7] 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 99
Error logged to Elmah.io!

What happened?

Unable to migrate pipeline using AzureDevOpsPipelineProcessor

Debug in Visual Studio

• Visual Studio Debug

[MrHinsh]

@tomfrenzel

[tiwarishrijan]

https://github.com/nkdAgility/azure-devops-migration-tools/blob/v16.0.7/src/MigrationTools.Clients.AzureDevops.Rest/Processors/AzureDevOpsPipelineProcessorOptions.cs

I do not see RepositoryNameMaps in AzureDevOpsPipelineProcessorOptions

[MrHinsh]

Im not sure but it should use the GitRepositoryTool.

[tiwarishrijan]

I am not into C# but i pointed as i don't see class variable RepositoryNameMaps defined in AzureDevOpsPipelineProcessorOptions class. Not sure how getter and setter method will set the value ?

Based on documentation i already have TfsGitRepositoryTool in configuration
"TfsGitRepositoryTool": {
"Enabled": true,
"Mappings": {}
},

[tiwarishrijan]

The logs shows error in line 386 which is if condition and only assumption i can make as of now is the value of RepositoryNameMaps is being set to null causing it to fail.

[MrHinsh]

Ahh... a fix in place...