1

I am working with Azure pipelines where the microservice has a dependency which has different versions.(Example: abc-1.0.1, abc-1.0.2) How should I store those dependency in Azure Devops

I came across The Universal Package task, which is currently not supported with Azure Devops Server. How should be the versioning of packages(created by gradle build) maintained while working with Azure Devops Server.

As currently different versions of build/jar is required by microservices. In order to maintain those versions, names, what is the best way in Azure Devops. (Note: As mentioned we are working with Azure Devops Server, not Azure Devops Services)

Priyanka Sharma
  • 87
  • 11

1 Answers1

1

The Universal Package task is not totally unsupported on Azure DevOps Server. It can be available on TFS 2018, Azure DevOps Server 2019 and Azure DevOps Server 2020.

enter image description here

So, if the version of your Azure DevOps Server (TFS) is TFS 2018 or later, you can use this task in your pipeline as normal.

If your TFS version is lower than TFS 2018 and does not support using the Universal Package task, you can try to call the Azure CLI "az artifacts universal" in the pipeline to publish and download the Universal Packages.

Bright Ran-MSFT
  • 5,190
  • 1
  • 5
  • 12
  • 1
    Hi, when I add Universal Package task to my pipeline yaml, it throws error "##[error]Failed to get artifact tool. Universal Packages are not supported in Azure DevOps Server. Finishing: UniversalPackages" Should I try with az commands in this case ? – Priyanka Sharma Jul 03 '22 at 09:59