To my understanding, DownloadBuildArtifacts@0 is legacy and DownloadPipelineArtifact@2 is preferred.
However, I'm getting the following warning when using the _latter_:
[warning]Please use Download Build Artifact task for downloading Build Artifact type artifact. https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/download-build-artifacts?view=azure-devops
The documentation for neither tasks explains which I need to use, when and why.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@abatishchev Thank you for the question.
The recommended approach is to use Download Pipeline Artifact task, please try using it with the Publish Pipeline Artifact task to eliminate this error.
Also, as a good comparison between the two, see this post on Stack Overflow.
Assigning this to the author for review of the current documentation.
@msebolt thanks for the info! Did I understand correctly that the warning is misleading: instead of switching from DownloadPipeline to DownloadBuild, I rather should switch from UploadBuild to UploadPipeline?
@msebolt, @vijayma gentle ping.
Right now if artifacts were uploaded using legacy "upload build" but downloaded using modern "download pipeline", the latter will show wrong, misleading warning message:
[warning]Please use Download Build Artifact task for downloading Build Artifact type artifact.
Instead it should display this one:
[warning]Please use Publish Pipeline Artifact task for downloading artifacts using Download Pipeline artifacts.
@msebolt, @vijayma gentle ping.
This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.
@msebolt, @vijayma so nothing has changed in 180 days even and now the issue is just closed by a bot. How cool is this?
Most helpful comment
@msebolt, @vijayma gentle ping.
Right now if artifacts were uploaded using legacy "upload build" but downloaded using modern "download pipeline", the latter will show wrong, misleading warning message:
Instead it should display this one: