Skip to main content

Azure DevOps Server–Agent download location has changed

It seems that I’m a little behind on what has changed in Azure DevOps Server recently. While helping my team migrate our existing build servers to some new infrastructure, we encountered a problem when trying to download the agent binaries.

When trying to download the agent binaries (available through Collection Settings –> Agent pools –> Default pool –> Agents –> New agent), it failed with a 404.

The URL used was:

Now if you are unlike me, you have probably followed up all Azure DevOps related announcement so you didn’t miss this announcement mentioning:

The current content delivery network (CDN) provider Edgio, used by Azure DevOps is retiring. We’re urgently transitioning to a solution served by Akamai and Azure Front Door CDNs to maintain the responsiveness of our services.

Whoops! I certainly missed that one…

The new URL is this:

https://download.agent.dev.azure.com/agent/3.238.0/vsts-agent-win-x64-3.238.0.zip

The recommended way to fix this problem is by applying the correct patch depending on your Azure DevOps server version:

Remark: For Azure DevOps Server 2022.2 a Patch 6 is already available but there are some issues mentioned about this patch version, so it is best to stick to Patch 5 for the moment.

More information

Deploy an Azure Pipelines agent on Windows - Azure Pipelines | Microsoft Learn

CDN Domain URL change for Agents in Pipelines - Azure DevOps Blog

Important: Switching CDN providers - Azure DevOps Blog

Labels:

Popular posts from this blog

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

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