AzureDevOpsPipelineProcessor

[giscus[bot]]

This discussion is for questions, feedback, and community support related to the Azure Dev Ops Pipeline Processor.

Quick Reference

• Class Name: AzureDevOpsPipelineProcessor
• Friendly Name: Azure Dev Ops Pipeline
• Documentation: Azure Dev Ops Pipeline Processor

How to Use This Discussion

• Ask Questions: If you need help configuring or using this component
• Share Examples: Post your configuration examples or use cases
• Report Issues: Describe any problems you encounter (though bugs should be reported as GitHub Issues)
• Request Features: Suggest improvements or new features

Related Documentation

Please refer to the official documentation for detailed configuration options and examples.

[hokkolo]

I am using version 16, I'm a bit confused on how to define the Source and Target details here.

[MrHinsh]

Yup, no problem... the sample is from the old version of the config. Here is what it might look like in the new system:

{
  "Serilog": {
    "MinimumLevel": "Debug"
  },
  "MigrationTools": {
    "Version": "16.0",
    "Endpoints": {
      "Source": {
        "EndpointType": "AzureDevOpsEndpoints",
        "Organisation": "https://dev.azure.com/nkdagility-preview/",
        "Project": "migrationSource1",
        "AuthenticationMode": "AccessToken",
         "AccessToken": "xxxxxx"
        }
      },
      "Target": {
        "EndpointType": "AzureDevOpsEndpoints",
        "Organisation": "https://dev.azure.com/nkdagility-preview/",
        "Project": "migrationTest5",
        "AuthenticationMode": "AccessToken",
        "AccessToken": "xxxxxx"
      }
    },
    "Processors": [
      {
        "ProcessorType": "AzureDevOpsPipelineProcessor",
        "BuildPipelines": "",
        "Enabled": "False",
        "MigrateBuildPipelines": "True",
        "MigrateReleasePipelines": "True",
        "MigrateServiceConnections": "True",
        "MigrateTaskGroups": "True",
        "MigrateVariableGroups": "True",
        "ReleasePipelines": "",
        "SourceName": "Source",
        "TargetName": "Target"
      }
    ]
  }
}

[hokkolo]

There are some minor syntax issues I faced while running the above config. For me the working Syntax is:-

{
    "Serilog": {
      "MinimumLevel": "Debug"
    },
    "MigrationTools": {
      "Version": "16.0",
      "Endpoints": {
        "Source": {
          "EndpointType": "AzureDevOpsEndpoint",
          "Organisation": "https://dev.azure.com/XXXX",
          "Project": "XXXX",
          "AuthenticationMode": "AccessToken",
          "AccessToken": "XXXXXXXX"
          },
        "Target": {
          "EndpointType": "AzureDevOpsEndpoint",
          "Organisation": "https://dev.azure.com/YYYY",
          "Project": "YYY",
          "AuthenticationMode": "AccessToken",
          "AccessToken": "YYYYYYYYY"
        }
      },
      "Processors": [
        {
          "ProcessorType": "AzureDevOpsPipelineProcessor",
          "BuildPipelines": "",
          "Enabled": "True",
          "MigrateBuildPipelines": "True",
          "MigrateReleasePipelines": "True",
          "MigrateServiceConnections": "True",
          "MigrateTaskGroups": "True",
          "MigrateVariableGroups": "True",
          "ReleasePipelines": "",
          "SourceName": "Source",
          "TargetName": "Target"
        }
      ]
   }
}

[shiva-gattu]

is there any way to migrate particular build and release with build ID and release ID

[MrHinsh]

As per the docs above:

BuildPipelines: List of Build Pipelines to process. If this is null then all Build Pipelines will be processed.
ReleasePipelines: List of Release Pipelines to process. If this is null then all Release Pipelines will be processed.

[YuriVanZieks]

I'm using the 16.3.0-Preview2 version of the Tool and I'm facing this message whenever I do a test for the PipeLine migration :

System.InvalidCastException: Impossible d'effectuer un cast d'un objet de type 'MigrationTools.Clients.TfsTeamProjectEndpoint' en type 'MigrationTools.Endpoints.AzureDevOpsEndpoint'. >> meaning impossible to cast object type MigrationTools.Clients.TfsTeamProjectEndpoint in type MigrationTools.Endpoints.AzureDevOpsEndpoint.

Manually changing does not correct this issue, and by default the file comes with "EndpointType": "TfsTeamProjectEndpoint".

How can this be solved ?

[MrHinsh]

The endoiubt for the Pipline migration is AzureDevOpsEndpoint

[sergeykrulikovskiy]

Hello,

I'm trying to understand if it is possible to migrate Pipelines from on-prem TFS to Azure Devops Services with this processor? If yes, can somebody provide an example of how should I configure sources endpoint for this case.
My server Version Dev17.M153.5
Tool version: 16.3

I've tried the following:

{
  "$schema": "https://devopsmigration.io/schema/configuration.schema.json",
  "Serilog": {
    "MinimumLevel": "Debug"
  },
  "MigrationTools": {
    "Version": "16.3",
    "Endpoints": {
      "Source": {
        "EndpointType": "AzureDevOpsEndpoint",
        "Organisation": "https://tfs-vm/Tfs-server-1/",
        "Project": "prj_name",
        "AccessToken": "xxxx",
        "AuthenticationMode": "AccessToken",
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId"
      },
      "Target": {
        "EndpointType": "AzureDevOpsEndpoint",
        "Collection": "https://dev.azure.com/sergey/",
        "Project": "TestMigration2",
        "AccessToken": "xxxx",
        "AuthenticationMode": "AccessToken",
        "Organisation": "https://dev.azure.com/sergey",
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId"
      }
    },
    "Processors": [
      {
        "ProcessorType": "AzureDevOpsPipelineProcessor",
        "Enabled": true,
        "SourceName": "Source",
        "TargetName": "Target",
        "MigrateBuildPipelines": true,
        "MigrateVariableGroups": true,
        "MigrateReleasePipelines": false
      }
    ]
  }
}

and got the following error:

System.Exception: Failed on call to get list of [ServiceConnection].
Url: GET https://tfs-vm/Tfs-server-1//prj_name/_apis/serviceendpoint/endpoints/?
Response Code:BadRequest
{"$id":"1","innerException":null,"message":"The requested version \"5.1\" of the resource is under preview. The -preview flag must be supplied in the api-version for such requests. For example: \"5.1-preview\"","typeName":"Microsoft.VisualStudio.Services.WebApi.VssInvalidPreviewVersionException, Microsoft.VisualStudio.Services.WebApi","typeKey":"VssInvalidPreviewVersionException","errorCode":0,"eventId":3000}
   at MigrationTools.Endpoints.AzureDevOpsEndpoint.<GetApiDefinitionsAsync>d__8`1.MoveNext() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.Rest\Endpoints\AzureDevOpsEndpoint.cs:line 214
--- 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.<CreateServiceConnectionsAsync>d__27.MoveNext() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 611
--- 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 74
--- 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 96
Error logged to Elmah.io!

Also I've tried to disable everything except build pipelines:

        "MigrateVariableGroups": false,
        "MigrateReleasePipelines": false,
        "MigrateServiceConnections": false,
        "MigrateTaskGroups": false

Response Code:BadRequest
{"$id":"1","innerException":null,"message":"The requested REST API version of 6.0 is out of range for this server. The latest REST API version this server supports is 5.1.","typeName":"Microsoft.VisualStudio.Services.WebApi.VssVersionOutOfRangeException, Microsoft.VisualStudio.Services.WebApi","typeKey":"VssVersionOutOfRangeException","errorCode":0,"eventId":3000}

Looks like my server is to old for this processor.
Thanks in advance.

[MrHinsh]

The Pipeline migrator only supports Azure DevOps and TFS 2022. TFS 2019 does not havet he required REST APIs.

[ram-grandhisila-alight]

I am using Azure Devops ,
i installed migration tool version 16.3.3(LTS)
this is my configuration.json file, i am trying to migrate classic release pipelines
configuration.json
{
"$schema": "https://devopsmigration.io/schema/configuration.schema.json",
"Serilog": {
"MinimumLevel": "Information"
},
"MigrationTools": {
"Version": "16.3",
"Endpoints": {
"PipelineSource": {
"EndpointType": "AzureDevOpsEndpoint",
"AuthenticationMode": "AccessToken",
"AccessToken": "xx",
"Organisation": "https://dev.azure.com/abc/",
"Project": "proj1",
"ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId"
},
"PipelineTarget": {
"EndpointType": "AzureDevOpsEndpoint",
"AuthenticationMode": "AccessToken",
"AccessToken": "xxxxx",
"Organisation": "https://dev.azure.com/xyz/",
"Project": "proj1",
"ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId"
}
},
"Processors": [
{
"ProcessorType": "AzureDevOpsPipelineProcessor",
"Enabled": true,
"MigrateBuildPipelines": false,
"MigrateReleasePipelines": true,
"MigrateTaskGroups": true,
"MigrateVariableGroups": true,
"MigrateServiceConnections": true,
"BuildPipelines": null,
"ReleasePipelines": null,
"RepositoryNameMaps": {},
"SourceName": "PipelineSource",
"TargetName": "PipelineTarget"
}
],
"CommonTools": {}
}
}
am getting following error, could some one assist on this please?

ERROR

[18:18:36 INF] [16.3.3] Azure DevOps Migration Tools [Object Model]
[18:18:36 INF] [16.3.3] 16.3.3
[18:18:36 INF] [16.3.3] naked Agility with Martin Hinshelwood
[18:18:36 INF] [16.3.3] ===============================================================================
[18:18:36 INF] [16.3.3] --------------------------------------
[18:18:36 INF] [16.3.3] Telemetry Note:
[18:18:36 INF] [16.3.3] We use Application Insights to collect usage and error information in order to improve the quality of the tools.
[18:18:36 INF] [16.3.3] Currently we collect the following anonymous data:
[18:18:36 INF] [16.3.3] -Event data: application version, client city/country, hosting type, item count, error count, warning count, elapsed time.
[18:18:36 INF] [16.3.3] -Exceptions: application errors and warnings.
[18:18:36 INF] [16.3.3] -Dependencies: REST/ObjectModel calls to Azure DevOps to help us understand performance issues.
[18:18:36 INF] [16.3.3] This data is tied to a session ID that is generated on each run of the application and shown in the logs. This can help with debugging. If you want to disable telemetry you can run the tool with '--disableTelemetry' on the command prompt.
[18:18:36 INF] [16.3.3] Note: Exception data cannot be 100% guaranteed to not leak production data
[18:18:36 INF] [16.3.3] --------------------------------------
[18:18:36 INF] [16.3.3] Start Time: "2026-02-02T18:18:36.1879910+05:30"
[18:18:36 INF] [16.3.3] Running with settings: {"ConfigFile":"configuration.json","DisableTelemetry":false,"DebugTrace":false,"skipVersionCheck":false,"$type":"ExecuteMigrationCommandSettings"}
[18:18:36 INF] [16.3.3] OSVersion: Microsoft Windows NT 6.2.9200.0
[18:18:36 INF] [16.3.3] Version (Assembly): 16.3.3
[18:18:36 INF] [16.3.3] Logpath: C:\Users\A1109602\AppData\Local\Microsoft\WinGet\Packages\nkdAgility.AzureDevOpsMigrationTools_Microsoft.Winget.Source_8wekyb3d8bbwe\logs\20260202181835
[18:18:41 INF] [16.3.3] Verion Info:
[18:18:41 INF] [16.3.3] Running: 16.3.3.0
[18:18:41 INF] [16.3.3] Installed: 16.3.3
[18:18:41 INF] [16.3.3] Available: 16.3.3
[18:18:41 ERR] [16.3.3] Configuration file 'configuration.json' is not valid against the schema.

Validation errors (deduplicated & filtered):

Likely root cause missing properties (all deduped candidate sets):
Path: MigrationTools.Processors[0]
- missing WIQLQuery (freq 4)

Path: MigrationTools.Processors[0]

• (Ln 27, Pos 7) Required: Required properties are missing from object: ResultFileName, WIQLQuery.
• (Ln 27, Pos 7) Required: Required properties are missing from object: WIQLQuery.
  Path: MigrationTools.Processors[0].BuildPipelines
• (Ln 35, Pos 30) Type: Invalid type. Expected Array but got Null.
  Path: MigrationTools.Processors[0].ProcessorType
• (Ln 28, Pos 55) Enum: Value "AzureDevOpsPipelineProcessor" is not defined in enum.
  Path: MigrationTools.Processors[0].ReleasePipelines
• (Ln 36, Pos 32) Type: Invalid type. Expected Array but got Null.

Total unique validation errors after filtering: 5

NOTE: A single missing property can trigger multiple branch (anyOf/allOf) mismatches. Fix the root cause lines above first.

[18:18:41 INF] [16.3.3] Command ExecuteMigrationCommand completed in "00:00:05.6909746"

[eerstenk-byte]

i could be wrong but i dont think under version 16.3.3 AzureDevOpsPipelineProcessor is working. the last update to this processor appears to be in november. i have tried various options which all complain with either WIQLQuery or invalid schema or authentication. can someone provide a working config for 16.3.3 ? desperate here as my company went bankrupt and we have to jump ship onto a new tenant...