YAML pipeline creation error workaround

YAML pipeline creation error workaround

Update
Mihaela Korte, 2/20/2025 7:27:06 PM

A subset of customers in certain geographies might encounter this error when trying to create a new YAML pipeline: “No template with an identifier of ‘xamarinandroid’ could be found”. While the fix for the issue is being rolled out, here are the workaround options:

[recommended, if possible, always go with this approach] Use the Pipeline creation REST API to create a new pipeline (see https://learn.microsoft.com/en-us/rest/api/azure/devops/pipelines/pipelines/create?view=azure-devops-rest-7.1) After creating it, you can continue editing in UI.

[if the first approach is definitely not applicable] Or through the UI:

  1. Disable the setting “Disable creation of classic build pipelines” on Organization/Project-level pipeline settings:
    YAML pipeline creation error workaround
  2. In pipeline creation UI, choose “Use the classic editor”:
    YAML pipeline creation error workaround
  3. Select the source repository, hit “Continue”
  4. Choose YAML as the template:
    YAML pipeline creation error workaround
  5. Choose a YAML definition (if any exists). If you don’t have any, create an empty YAML file in the repository.
  6. Save the pipeline. You now have a new pipeline, if you click on “Edit”, you can continue editing your pipeline in the regular YAML experience. Important: Set the switch back to its original state after the rollout is completed (ETA February 24).

We apologize for any inconvenience this issue might have caused.


Initial communication
Mihaela Korte, 2/20/2025 7:22:25 PM

A subset of customers in certain geographies might encounter this error when trying to create a new YAML pipeline: “No template with an identifier of ‘xamarinandroid’ could be found”. While the fix for the issue is being rolled out, here are the workaround options:

[recommended, if possible, always go with this approach] Use the Pipeline creation REST API to create a new pipeline (see https://learn.microsoft.com/en-us/rest/api/azure/devops/pipelines/pipelines/create?view=azure-devops-rest-7.1) After creating it, you can continue editing in UI.

[if first approach is definitely not applicable] Or through UI:

  1. Disable the setting “Disable creation of classic build pipelines” on Organization/Project-level pipeline settings
  2. In pipeline creation UI, choose “Use the classic editor”
  3. Select the source repository, hit “Continue”
  4. Choose YAML as the template
  5. Choose a YAML definition (if any exists). If you don’t have any, create an empty YAML file in the repository.
  6. Save the pipeline. You now have a new pipeline, if you click on “edit”, you can continue editing your pipeline in the regular YAML experience.
    Important: Set the switch back to its original state after the rollout is completed (ETA February 24).

We apologize for any inconvenience this issue might have caused.

Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *