Azure DevOps Server 2022 Update 2 RC now available
Today we’re thrilled to announce the release candidate (RC) of Azure DevOps Server 2022.2!
This release includes new features that have been previously released in our hosted version of the product. Here are a few of the highlights:
- Limits for area and iteration paths
- Bypass approvals and checks in pipelines
- Improved YAML validation
- Azure Artifacts support for Cargo Crates
- New Dashboard directory experience
- Quick Copy and import for Test Plan or Suite ID
There are more features with this release, and you can read all about those features in our release notes.
You can download Azure DevOps Server 2022.2 RC today. A direct upgrade to Azure DevOps Server is supported from any version of TFS, including Team Foundation Server 2015 and newer. Let us know any feedback or questions via the Developer Community.
Resources
- Download Azure DevOps Server 2022.2 RC
- Release notes
- Azure DevOps Server requirements and compatibility
- Installation documentation
10 comments
super minor but the “new agent” screen has the wrong version of the agent in the setup directions for the x64 zip:
PS C:\agent> Add-Type -AssemblyName System.IO.Compression.FileSystem ; [System.IO.Compression.ZipFile]::ExtractToDirectory(“$HOME\Downloads\vsts-agent-win-x64-3.225.0.zip”, “$PWD”)
x86/mac/linux are correct
PS C:\agent> Add-Type -AssemblyName System.IO.Compression.FileSystem ; [System.IO.Compression.ZipFile]::ExtractToDirectory(“$HOME\Downloads\vsts-agent-win-x86-3.225.3.zip”, “$PWD”)
Hi Jonathan, thank you for installing the Azure DevOps Server 2022.2 release candidate and reporting this. We will address this with the final version of Azure DevOps Server 2022.2.
Does Update 2 include a fix for this issue with Update 1? https://developercommunity.visualstudio.com/t/Known-issue:-Agent-version-does-not-upda/10534065
Hi, this issue has been fixed with Update 2.
Looking forward to fixes and new features 🙂
When you get to update the features timeline with the features introduced with 2022.2, then you might want to review the items market with ‘Future’ too:
https://learn.microsoft.com/en-us/azure/devops/release-notes/features-timeline-released
An example is the “Trigger CI builds from YAML”, which I figure have been included in ADO Server for many years:
https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/apr-16-vsts#trigger-ci-builds-from-yaml
Another example is “Removing older images in Azure Pipelines hosted pools” which I guess should be marked with “N/A” instead of “Future”:
https://learn.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-164-update#removing-older-images-in-azure-pipelines-hosted-pools
Thank you Tore for the feedback.
Hi
I wonder if you somehow know the status of the test framework included with this release. We have seen multiple problems in each release and although some things are fixed, then it just seems like new problems are added.
Current issue – Wrong failure naming for DynamicData:
https://developercommunity.visualstudio.com/t/AZDO-portal-can-report-incorrectly-faile/10497992
Current issue – Rerun failure:
https://github.com/microsoft/azure-pipelines-tasks/issues/16187
Previous issue – DataTestMethod rerun not correct
https://developercommunity.visualstudio.com/t/VSTest-rerun-logic-have-issues-with-Data/10292590
Thanks for the feedback. Both reported issues are related the VSTest@2 task. As soon as the root cause for each of the two cases will be identified and fixed, we’ll release new version of that task that will resolve these problems.
Will the team be on-site next week during Build in Seattle?
Would love to chat if you have time 🙂
Some of us will be there. See you at Build 🙂