Today we are releasing patches that impact our self-hosted product, Azure DevOps Server, as well as Team Foundation Server 2018.3.2. We strongly encourage and recommend that all customers use the latest, most secure release of Azure DevOps Server. You can download the latest version of the product, Azure DevOps Server 2022.2 from the Azure DevOps Server download page.
Previously, the Azure DevOps Agent used the Edgio CDN with endpoint vstsagentpackage.azureedge.net. As part of Edgio’s retirement, the vstsagentpackage.azureedge.net domain is being decommissioned. To ensure continued availability, we have migrated to an Akamai-backed CDN with a new endpoint download.agent.dev.azure.com. This patch includes the necessary changes to fetch the Agent binaries from the new CDN endpoint, thereby migrating away from the previous CDN endpoint.
Note: Domain retirement applies to the
vstsagentpackage.azureedge.netdomain only and not all*.azureedge.netdomains. You can learn more about the Azure CDN from Edgio retirement in the FAQ documentation.Important: The CDN Domain URL change for Agents in Pipelines blog provides steps to follow before installing this patch.
Azure DevOps Server 2022.2 Patch 5
If you have Azure DevOps Server 2022.2, you should install Azure DevOps Server 2022.2 Patch 5 to have the most secure product experience. Check out the Release notes for details.
Note: Azure DevOps Server 2022.2 is the latest version of Azure DevOps Server. If you have installed Azure DevOps Server 2022 or Azure DevOps Server 2022.1, you should first upgrade to Azure DevOps Server 2022.2 and then install Azure DevOps Server 2022.2 Patch 5.
Verifying Installation
Run devops2022.2patch5.exe CheckInstall, devops2022.2patch5.exe is the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that it is not installed.
Additional versions that we patched
The versions of Azure DevOps Server and Team Foundation Server listed in the table below have also been patched. Check out the links in the Release Notes column for each version to install each patch.
| Version | Release Notes |
|---|---|
| Azure DevOps Server 2020.1.2 | Patch 16 |
| Azure DevOps Server 2019.1.2 | Patch 11 |
| Team Foundation Server 2018.3.2 | Patch 20 |
We are currently running Azure DevOps 2020 Update 1.2 (18.181.32404.7), and need to move to DevOps 2020 Update 1.2 Patch 16.
Are the patches cumulative patches, meaning we just need to install patch 16? Or does each patch need to be installed in order, from 1 through to 16?
Thanks, Jason
Hi Jason. You can install Azure DevOps Server 2020.1.2 Patch 16 without having to install previous patches.
Hi Gloridel,
We are using Azure DevOps 2019 Update 1.1 Patch 13.
Could our update path be :
-Update 1.2
-Update 1.2 Patch 11
Are the fixes cumulatives or do we have to install each of them in order ?
Thanks,
Jeff
Hi Jeff, patches are cumulative. The path that you describe is correct, you will have to upgrade to Azure DevOps Server 2019.1.2 and then install Patch 11.
Hi Gloridel,
Is there a way to identify that Patch 11 (Azure DevOps Server 2019 Update 1.2) has been installed ?
The installation log says so without errors, but is there a file version i could check ?
Thanks !
Jeff
Thanks for the quick reply Gloridel and your answer is a relief !!!
Jeff
we are currently on Azure DevOps Server 2022.1 Patch 4 due to the new minimum SQL Server 2019 requirements in version 2022.2 and we can’t upgrade SQL Server at the moment and therefore not upgrade to 2022.2
Is it possible to manual update the TFS configuration with the new CDN domain?
what is the planned release date for the next major Azure DevOps Server as we want to upgrade directly to that version when it will be available within a reasonable time frame?
Hi Daniel, I forwarded your question about manually updating the TFS configuration to our engineer team. I will let you know as soon as I have a response.
We are planning on releasing RC late summer, and RTW in Q4 this year.
Hello Gloridel,
I am using Azure Devops 2022.0.1. Does the CDN change apply to this version as well?
Do i have to upgrade to 2022.2?
Hi Sarita, it applies to all Azure DevOps Server 2022 versions that we have released. You will have to upgrade to the latest version (Azure DevOps Server 2022.2) and then install the patch.
The download link for the patch on the 2022 Update 2 Patch 5 release notes page seems to be broken. The link in the page above works though.
Hi Matthew, there was a typo in the download link, and it has been corrected. Thank you for reporting the issue.
What exactly is applied by the patch?
Some settings in the “background” of the AzDO server, or does the patch replace the build agent (ba) version?
If it only replace the ba, to which version will be the ba updated?
May by we have already rolled out the right version 🤞
Hi Markus, the patch does not replace the build agent. The patch replaces TFS configuration which is essential to provision/update the agents using the new CDN domain.