2

We recently migrated our Pipelines to different Org using Azure DevOps Migration Tool. The Migration itself was successful and we can see all the migrated pipeline in Destination project. But encounter an error "No spool was specified" while running the migrated pipelines.

Does anyone face this issue with the Azure DevOps Migration tool?

I tried by creating a new pipeline in Destination project to check its working and it worked with no issues.

The issue getting only with the migrated pipelines.

stackuser
  • 21
  • 1

1 Answers1

2

Encounter an error "No pool was specified" while running the migrated pipelines

Based on the error message, it seems that the migrated pipelines no agent specified。

You can edit the migrated pipelines and check the agent pool.

enter image description here

Then you can save the pipeline and run again.

Update:

For Yaml Pipeline, you can navigate to Edit Pipeline -> ... -> Triggers -> YAML -> Pipeline -> Default agent pool for YAML

enter image description here

enter image description here

Kevin Lu-MSFT
  • 20,786
  • 3
  • 19
  • 28
  • I can't see the exact screen when doing the EDIT pipeline. I see the YAML code. The above attached screenshot i see when i create a new pipeline using classic editor. But under Project Settings-->Agent Pools , i can see that my migrated pipelines trying to run against Azure Pipeline Agent but throwing No pool was specified error – stackuser Mar 23 '22 at 16:48
  • @stackuser Please check my update about YAML pipeline. You can share the result with me – Kevin Lu-MSFT Mar 24 '22 at 06:53
  • 1
    Thanks Kevin.. Yes i can see the option now and it solved my problem too. – stackuser Mar 24 '22 at 18:33
  • Kevin.. I have successfully migrated 100's of pipeline via azure migration tool but somehow the Agent pool is not set to Azure Pipeline automatically. I have to follow your steps manually for each one of them in order to get my migrated pipeline work. Wondering , is there any settings in migration tool OR any other automatic way where i can set up the Agent pool all at once rather than going one by one ? – stackuser Apr 19 '22 at 18:12
  • @stackuser Consider going to this issue on the feedback hub and commenting on the "solution" to let Microsoft know we'd like this fixed. We shouldn't have to do a workaround. https://developercommunity.visualstudio.com/t/Auto-created-pipeline-from-yaml-return-e/10054547?q=yaml+no+pool+was+specified – Keith Banner Jan 07 '23 at 01:04