Today, we are releasing multiple versions of our self-hosted product, Azure DevOps Server. You can find the details of the fixes in the release notes for each version.
Today, we are releasing multiple versions of our self-hosted product, Azure DevOps Server. You can find the details of the fixes in the release notes for each version.
Gloridel is a Senior Technical Program Manager on the Azure DevOps team.
Concerning 2020.1.2 installer:
In the following readiness check message from the installer, the link is not working
Also the “hardware requirements and installation notes” from the search configuration page lead to https://go.microsoft.com/fwlink/?linkid=2042270. This also results in a 404.
There are probably more links inside the installer invalid
Can we directly upgrade to Azure Devops Server 2020.1.2 from Azure Devops Server 2020.0.1( 18.170.30.910.2 )
We’re directly upgrading from Azure DevOps Server 2019.1.1 to Azure Devops Server 2020.1.2 without problems, so doing it from 2020.0.1 should work just fine too 😉
Is the Active Directory sync problem mentioned in the comments of this devblog here:
https://devblogs.microsoft.com/devops/azure-devops-server-and-team-foundation-server-patches/
now fixed with this 2020.1.2 release?
Thanks in advance…
As far as I’ve seen in our test update installation of the Azure DevOps 2020.1.2 release we do not have a problem with the synchronization of active directory users or groups and the ‘Team Foundation Server Periodic Identity Synchronization’ job doesn’t take longer as on the Azure DevOps 2019 installation (in fact it’s even a second faster). So it seems this problem has been fixed, though I didn’t have the chance to ever test if it happened for us with a 2020.1.1 installation.
Since the Release Notes does not mention support for Visual Studio 2022, does that mean that it is not included?
Really waiting for that to avoid installing newer version of the agent manually.
Thank you for sharing your solutions, but I was looking for an answer on the ability of Visual Studio 2022 support out-of-the-box.
It was released November 8th of last year so half a year has passed now since Visual Studio 2022 was released. Best would of cause be if the versions was not hardcoded so that support would be present on release.
You can update the build agent within Azure Devops Server by uploading to %ProgramData%\Microsoft\Azure DevOps\Agents on your Azure Devops app server.
You can read more here: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops-2019&tabs=browser#can-i-update-my-v2-agents-that-are-part-of-an-azure-devops-server-pool
After you make an agent version available at that path, Azure Devops Server will automatically propagate the update out to existing agents.
We use this task until the official release:
https://marketplace.visualstudio.com/items?itemName=jessehouwing.visualstudio
It’s actually based out of Microsoft’s repo of AzDO tasks.