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.
Hi Gloridel, I am planning an upgrade from Azure DevOps Server 2020.1 to Azure DevOps Server 2022.2. Now that the Update 2 RC has been out for over one month can you provide any update on when we can expect the 2022.2 RTW (soon, few weeks, over 1 month)? Thanks
Hi Steven, Azure DevOps Server 2022.2 RTW is now available.
Hi Steven, we plan to release within the next two weeks.
I see this issue… https://developercommunity.visualstudio.com/t/Blank-page-when-accessing-Team-configura/10661411 is now closed and it states that “We have released a fix for this issue! Thank you for providing valuable feedback to help improve the product.” .. but it does not indicate how I can download the fix to test it.. can you provide that information?
Thanks
Steven
Hi Steven, we plan to release RTW tomorrow. You will be able to download from the Azure DevOps Server download page.
Hi Gloridel, I was able to perform a test upgrade but found a issue that would prevent my upgrade.
The issue I encountered was previouly reported in this thread...
https://developercommunity.visualstudio.com/t/Blank-page-when-accessing-Team-configura/10661411?q=Team+configuration
... I think it may be releated to a custome process template which specifies a custom team field on the work-items. I have added to that thread my details.
This issue would prevent me from proceeding with the upgrade so can you check to confirm this...
Hi Gloridel, can you check on the issue that is reported in this post… https://developercommunity.visualstudio.com/t/Blank-page-when-accessing-Team-configura/10661411?q=Team+configuration&viewtype=all to confirm it will be addressed in the next release of 2022.2?
Thanks
Steven
how to upgrade from 2022.1 to this one.
Hi Murat, the following article outlines the steps to upgrade.
Upgrade your deployment to the latest version of Azure DevOps Server
Update produces error:Read more
[31C4:21F0][2024-06-11T16:31:58]i338: Acquiring package: launchTfsMgmt, payload: launchTfsMgmt, copy from: H:\packages\LaunchTfsMgmt\LaunchTfsMgmt.exe
[3608:3208][2024-06-11T16:31:58]i305: Verified acquired payload: launchTfsMgmt at path: C:\ProgramData\Package Cache\.unverified\launchTfsMgmt, moving to: C:\ProgramData\Package Cache\A94D01BD9EC9F3D0943A113C66E28C791D7172B2\packages\LaunchTfsMgmt\LaunchTfsMgmt.exe.
[31C4:21F0][2024-06-11T16:31:58]i000: MUX: Source confirmed
[3608:3270][2024-06-11T16:34:35]e000: Error 0x80073e80: Process returned error: 0x3e80
[3608:3270][2024-06-11T16:34:35]e000: Error 0x80073e80: Failed to execute EXE package.
[31C4:18E4][2024-06-11T16:34:35]e000: Error 0x80073e80: Failed to configure per-machine EXE package.
[31C4:18E4][2024-06-11T16:34:35]i000: MUX: Installation size in bytes for package: PrepareTFSInitialize MaxAppDrive: 0 MaxSysDrive: 2637287 AppDrive: 0 SysDrive: 2637287
Carsten,
sorry that you are having difficulties with Azure DevOps. Can you share specs for your machine (CPU/RAM/SSDvsHDD)?
We saw this issue on very underpowered machines.
To continue configuration you can execute the following command: “c:\Program Files\Azure DevOps Server 2022\Tools\TfsMgmt.exe” configure
Thanks,
–Vladimir
It’s not related to server specs at all.
Problem exists also in 2022.1
https://developercommunity.visualstudio.com/t/Package-failed-when-upgrading-Azure-DevO/10529088?sort=newest
It is also not related to Analytics. Workaround is uninstall and fresh install works, as “only” upgrade fails.
Nobody is willing to properly investigate why uninstall/install is working and upgrades are failing.
case: 2402200030005195
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 🙂
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.
Hi Bohdan
There are very little news on those issues.
Can we help in any way to reproduce the issue?
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...
Thank you Tore for the feedback.
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 Maple, Azure DevOps Server 2022.2 RTW is now available.
Hi, this issue has been fixed with Update 2.
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, Azure DevOps Server 2022.2 RTW is now available.
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.