Skip to main content

Azure Pipelines - Failed to download task 'Download'

I’m working on converting an Azure DevOps Release pipeline to a yaml pipeline. As a first step in my pipeline I want to download the build artifacts so I can use them in my release pipeline. However using this task resulted in an error message. Let's find out what was causing this…

You can download an artifact in your pipeline through the ‘Download Pipeline Artifacts task’. You can use this task as a step in your pipeline or you can use the shorthand ‘download’ alias:

Executing the pipeline above resulted in the following error message:

Failed to download task 'Download'. Error No task definition found matching ID 30f35852-3f7e-4c0c-9a88-e127b4f97211 and version 1.0.0. You must register the task definition before uploading the package.

This error message is quite misleading and would make you think that there is something wrong with downloading the ‘Download’ task (which turned out not to be the issue).

Let’s take a closer look at our yaml pipeline. We have set our pipeline resource name to ‘example_ci’. Notice the underscore:

When we refer to this resource in our download task I've used 'example-ci':

So the problem was caused by the fact that I was referring to a resource that wasn’t defined (because I made a typo). The fix was easy, I updated the download step to use the correct resource name:

Problem solved!

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more