[Bug]: Pipeline Processor returning "UnsupportedMediaTypeException" about azure-devops-migration-tools

[MrHinsh]

It sounds like 5.1 does not support the features being accessed. 6.0 would be the minimum...

You would need to use 7.2 if 6 is no longer supported.... but Im not sure what 2019 supports

[raquelgarciag]

I see - thanks for your help!

[norschel]

@MrHinsh You find the current REST API - AzD version mapping table at Mapping Table. 2019 only supports REST API version 5.x.

[MrHinsh]

Then it looks like the pipeline migrator is not supported in 2019. We need 6.1+ for it to work.

@norschel is there a way to detect the version of TFS from the API?

[madhuripawar2212]

Hi Everyone,

I am using the migration tool to migrate the pipelines from one organization to another in Azure Devops. I am getting the below error. Can anyone please help me with this?

[15:09:40 FTL] Error while running AzureDevOpsPipelineProcessor
System.NullReferenceException: Object reference not set to an instance of an object.
at MigrationTools.Processors.AzureDevOpsPipelineProcessor.d__17.MoveNext() in D:\a\1\s\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 MigrationTools.Processors.AzureDevOpsPipelineProcessor.d__9.MoveNext() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 95
--- 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 MigrationTools.Processors.AzureDevOpsPipelineProcessor.InternalExecute() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 49
at MigrationTools.Processors.Processor.Execute() in D:\a\1\s\src\MigrationTools\Processors\Processor.cs:line 106

[MrHinsh]

Please create a new thread @madhuripawar2212; this is a different topic.

When you do post, attach your config and logs.

[norschel]

Then it looks like the pipeline migrator is not supported in 2019. We need 6.1+ for it to work.

@norschel is there a way to detect the version of TFS from the API?

In case of WorkItemMigrationConfig, you can ask the TfsProjectCollection class for serverversion, e.g.:

y = new TfsTeamProjectCollection(TfsConfig.Collection);
Log.Debug(y.ServerDataProvider.ServerVersion);

The result is for example:
ServerVersion = "Dev19.M225.3" (AzD 2022) .

For the REST API you can call any REST API (without providing the api-version) and then check the content-type of the response header. The result in this case is for example:
Content-Type: application/json; charset=utf-8; api-version=5.1-preview.1

[MrHinsh]

@tomfrenzel perhaps adding a kill switch in the event of an older API!

[UzairKhan2598]

@MrHinsh I am getting the same error while migrating pipelines, please help
Version - 12.0
Source - azure devops server 2019
Target - azure devops services
Error -
{"$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}

[MrHinsh]

The pipeline migrator needs a minimum of V6 of the Rest API.

Your version of TFS is not supported.

[github-actions]

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