[Question]: Self-hosted Azure DevOps Server cannot use specific task version

[Varorbc]

Task name

DotNetCoreCLI@2

Task version

2.266.0

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

Azure DevOps Server (Please specify exact version in the textbox below)

Azure DevOps Server Version (if applicable)

Azure DevOps Server 2022.2

Operation system

Windows Server 2019

Question

@tarunramsinghani

When using Azure DevOps Pipelines, I noticed the following behavior:

• In Azure DevOps Services (cloud), a specific task version runs successfully.
• In our self-hosted Azure DevOps Server environment, the same task version cannot be used.

My question is: does the self-hosted environment require additional configuration or update steps? Do we need to manually synchronize marketplace extensions or task versions? What settings should we check to ensure consistency between Azure DevOps Server and Azure DevOps Services when using tasks?

[jessehouwing]

The tasks aren't automatically released on Azure DevOps Server.

You either need to wait for a patch to be released (e.g. 2022.3) or upgrade to the next major version of Azure DevOps Server for official support.

You can also manually push the tasks to Azure DevOps Server, or use one of my compatibility extensions:

https://github.com/jessehouwing/azure-pipelines-tasks-zips/

And you may need to install the latest version of the agent (and disable automatic downgrades) to ensure the correct capabilities are detected.