Azure DevOps Server 2022 Update 2 RC now available

Gloridel Morales

May 7th, 202420 6

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:

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

Gloridel Morales Senior Technical Program Manager, Azure DevOps

Read next

20 comments

Leave a comment

  • Jonathan Gillette 0

    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”)

    • Gloridel MoralesMicrosoft employee 0

      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.

  • Tore Østergaard Jensen (TORE) 0

    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

  • Tore Østergaard Jensen (TORE) 0

    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

    • Bohdan JanousekMicrosoft employee 0

      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.

      • Tore Østergaard Jensen (TORE) 0

        Hi Bohdan

        There are very little news on those issues.

        Can we help in any way to reproduce the issue?

  • Tore Østergaard Jensen (TORE) 0

    Will the team be on-site next week during Build in Seattle?

    Would love to chat if you have time 🙂

  • Carsten Krüger 0

    Update produces error:
    [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
    [31C4:18E4][2024-06-11T16:34:35]i000: MUX: Return Code:0x80073E80 Msi Messages:0 Result Detail:0 Restart:None
    [31C4:18E4][2024-06-11T16:34:35]i000: MUX: Set Result: Return Code=-2147008896 (0x80073E80), Error Message=, Result Detail=, Vital=False, Package Action=Install, Package Id=PrepareTFSInitialize
    [31C4:18E4][2024-06-11T16:34:35]i000: Setting string variable ‘BundleResult’ to value ‘0’
    [31C4:18E4][2024-06-11T16:34:35]w350: Applied non-vital package: PrepareTFSInitialize, encountered error: 0x80073e80. Continuing…
    [31C4:18E4][2024-06-11T16:34:35]i000: MUX: ExecutePackageBegin PackageId: devops_serverCore

    • Vladimir KhvostovMicrosoft employee 0

      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

  • Murat Ozer 0

    how to upgrade from 2022.1 to this one.

  • Markowitz, Steven 0

    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

Feedback usabilla icon