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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more