Release Pipeline pulling DownloadBuildArtifact Task v1.188.0 | Failing

[codytipton-hpg]

Question, Bug, or Feature?
Type: Question, potentially bug

Enter Task Name: DownloadBuildArtifact

Environment

Azure Pipelines

Issue Description

Our release pipelines began failing today and the logs are marked by a new version of the download build artifact task, specifically v1.188.0. Prior to today we were pulling, most recently, v0.186.3 and deploying successfully.

I'm not sure how we're picking up this version on the backend, since the task version is not configurable for Release pipelines, at least as far as I can see.

Task logs

I'm unsure how to enable debug logging for Release pipelines.

Other observations

I noticed this Open PR #14560 defining a version 1.188.0 and suspect it may be relevant, though I'm unsure how we're pulling this (or similarly versioned) task.

[anatolybolshakov]

Hi @codytipton-hpg I can't reproduce it at the moment using yaml and release pipelines - do you still see this issue?

[codytipton-hpg]

Hi @anatolybolshakov,

Yes, we are still facing the issue. I also updated the target agents (2.177.1).

When you test, is your DownloadBuildArtifacts Task for the release pulling version 1.188.0 as well?

As a note, for the associated builds producing the artifacts, we're using PublishBuildArtifacts Task v1

[codytipton-hpg]

@anatolybolshakov

Update: I found a workaround by using the PublishPipelineArtifact Task in my builds. Releases will thus use the DownloadPipelineArtifact task over the DownloadBuildArtifact Task, avoiding the issue.

Looking at this issue comment I see that the task is intended to replace PublishBuildArtifacts anyway, so I will begin opening PR's to update the publish step. Still, this does seem like breakage of functionality. I'll defer to you for whether or not the issue should remain open.

[alex-peck]

This is caused by an out of date agent. When the new task is used, it should request your agents to automatically update. Is your system configured to block agent updates?

[codytipton-hpg]

This is caused by an out of date agent. When the new task is used, it should request your agents to automatically update. Is your system configured to block agent updates?

At the time of the issue, updating the agent on both build server and the deployment target did not resolve. Though I'm prepared to believe a later agent update resolves this issue, we've moved to PublishPipelineArtifact tasks and don't have a need to revert and retest PublishBuildArtifacts.