CODEWITHSUNDEEP
azure-devopsazure-pipelinestfx
AhmadYo
AhmadYo

Reputation: 476

Azure Devops custom pipeline task updating to new version passed verification but actually failed without any error and not using updated version

This question is about writing custom pipeline task for Azure DevOps Server (On Premises) (Add a custom pipelines task extension). I wrote my task with PowerShell and installed it and it's working well but updating to new version (patch number) not worked. Updating to new patch version was successful and verified OK, and in Manage Extensions page shows the new version is installed, either in Installed extensions page. But in pipeline definition It not accepts to save definition of a pipeline with new version and says task is missing also agents not using new version and still using old version. This process was successful for previous versions of this task, and updating of it occurred many times but at this new version failed. How can I debug the Update process of extension to new version? Where can I see the log if any exists?

I tried to install it with tfx cli but other problems stopped me like error: unable to get local issuer certificate

(Azure DevOps Server 2022.2 ver: 20240702.1)

Update - Workaround: Restarting the Azure DevOps Server solved the problem, and some of uploaded patch versions now available to use but not all of them, and more importantly, this is not a conventional solution.

Upvotes: 0

Views: 151

Answers (1)

Ziyang Liu-MSFT
Ziyang Liu-MSFT

Reputation: 4967

Please ensure that the version in your task.json file has been updated and your extension is created based on the new version. enter image description here

The version you see in Installed extensions page and Manage Extensions page is the version of your extension, which is defined in vss-extension.json.

enter image description here

If I update the version in vss-extension.json, but not in task.json, I will reproduce your issue.

Update:

Solution (shared by @AhmadYo):

Restarting the Azure DevOps Server solved the problem.

Restarting the server can force all services and applications to reload, ensuring that the new version of your extension is properly initialized and running.

Upvotes: -1

Related Questions