July patches for Azure DevOps Server
Gloridel Morales
This month, we are releasing fixes that impact our self-hosted product, Azure DevOps Server.
The following will be fixed with this patch:
- In Test Runs APIs, the continuation token being returned was greater than the “maxLastUpdatedDate” value that was specified.
- While editing a classic pipeline, the retention tab was blank after discarding changes on a different tab.
Azure DevOps Server 2020.1.2 Patch 1
If you have Azure DevOps Server 2020.1.1, you should first update to Azure DevOps Server 2020.1.2. Once on Update 1.2, install Azure DevOps Server 2020.1.2 Patch 1. Check out the release notes for more details.
Verifying Installation
- Run
devops2020.1.2patch1.exe CheckInstall,devops2020.1.2patch1.exeis 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.
Azure DevOps Server 2019.1.2 Patch 1
If you have Azure DevOps Server 2019 Update 1.1, you should first update to Azure DevOps Server 2019.1.2. Once on Update 1.2, install Azure DevOps Server 2019 Update 1.2 Patch 1. Check out the release notes for more details.
Verifying Installation
- Run
devops2019.1.1patch1.exe CheckInstall.devops2019.1.1patch1.exeis 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.
Light
Dark
10 comments
Is there a timeplan for the release of Azure DevOps Server 2022? Will there be (a) release candidate(s)?
Hi Michael, we will have two release candidates for Azure DevOps Server 2022 and we plan to ship RC1 late summer.
Thank you
Interesting in learning what the minimum Windows Server OS and SQL Server versions are.
At this point, should it be named Azure DevOps Server 2023? 🙂
Looking forward to the update!
Where is the DataMigration tool update for version 2020 Update 1.2?? Its been over three weeks since release?
Hi Jason, migration is now supported for Azure DevOps Server 2020.1.2.
We published this today. It might take a few hours for it to replicate it through CDN to be available everywhere.
Hi,
We use the latest version of Server 2020 – 1.2 patch 1 (10.181.32407.7), and the latest version of the migration tool ( DataMigrationTool_AzureDevOps2020.1.2RTW_18.181.17674990.zip)
Despite of this, we are unable to migrate to cloud and we got the following error:
Import couldn’t be started due to an error!
[Error] VS403265: The collection’s Azure DevOps Server milestone is not supported by the data migration tool: Azure De
vOps Server 2020 Update 1.2 (Dev18.M181.9). Please upgrade your Azure DevOps Server to one of the supported versions. Th
e data migration guide has the latest supported versions: https://aka.ms/AzureDevOpsImport
How can we solve this? Thank you.
Hi Gloridel,
Is there a patch or update in the works that delivers official support for Visual Studio 2022?
Right now we cannot use the build tasks and target Visual Studio Tools 2022, as the latest known version is 2019.
For more information, please see https://jessehouwing.net/adding-visual-studio-2022-to-azure-devops-server-2020/
Hello, I updated from 2020.1.1 Patch 4 to 2020.1.2 and immediately installed Patch 1. Searching my server no longer searches Work Items, only code in my Git repo. What do I need to do to get search fully working again?
I have reinstalled the Work Item Search extension from the MarketPlace and no luck. When I click on the Work item sub category after performing a search, I get “We encountered an unexpected error when processing your request
Try searching again and contact your administrator if the problem persists”
Many thanks!
new info: I followed the instructions here: https://stackoverflow.com/questions/64995180/azure-devops-server-2020-reconfigure-search and I believe it is working again. MS’ documentation mentions that it is possible to re-run the search configuration, but doesn’t give information for how to do so. Thanks to the stack overflow poster for showing how!
FYI, I forgot my searchuser password when I ran the 2020.1.2 update. I reset the password while I was performing the 1.2 update and specified the new password when I configured the 2020.1.2 update. Perhaps this why my search broke. Once I found the Stack Overflow information, I ended up uninstalling the elastic search service, re-ran the search configuration selecting a new folder to host the search indices and now it seems to be happy. I am waiting for it to reindex my server, but that will likely take a couple of hours.