AzureDevOpsPipelineProcessor: Release definitions: issue with artifact aliases

[limak9182]

I want to migrate release definitions form one project in one org to another. I encountered this kind of issue, Do you know if there is other than manual way of migrating this?
Error:

[10:58:16 ERR] Error migrating ReleaseDefinition: xxx. Please migrate it manually.
Url: POST https://vsrm.dev.azure.com/xxx//xxx/_apis/release/definitions/
{"$id":"1","innerException":null,"message":"Artifact alias 'xxx' does not matching any linked artifact aliases for deploy job 'Deployment group job'. Specify a valid artifact alias and try again.","typeName":"Microsoft.VisualStudio.Services.ReleaseManagement.Data.Exceptions.InvalidRequestException, Microsoft.VisualStudio.Services.ReleaseManagement2.Data","typeKey":"InvalidRequestException","errorCode":0,"eventId":3000}

My configuration:

"Processors": [
      {
        "$type": "AzureDevOpsPipelineProcessorOptions",
        "Enabled": true,
        "MigrateBuildPipelines": true,
        "MigrateReleasePipelines": true,
        "MigrateTaskGroups": true,
        "MigrateVariableGroups": true,
        "MigrateServiceConnections": false,
        "BuildPipelines": null,
        "ReleasePipelines": null,
        "RefName": null,
        "SourceName": "Source",
        "TargetName": "Target",
        "RepositoryNameMaps": {}
      }
    ]

I use 13.0.4.0 version and Azure DevOps service in both instances.

[MrHinsh]

Perhaps @tomfrenzel may have an idea!

[rppwolfs]

I am encountering exactly the same issue here.
Could the error be caused because the Target project does not contain any artifacts yet ?

[AviramDahan]

any news ?

[bensgroi]

@limak9182 - did you ever find a workaround or solution for this issue? I'm encountering it too.

[jmjacobs1982]

The workaround I found was to delete the artifact alias from the release. Then migrate it. Then add it back.

[MrHinsh]

@tomfrenzel ?