July 9th, 2024

Updated: Azure DevOps Server 2022.2 RTW now available

Gloridel Morales
Gloridel Morales
Senior Technical Program Manager

8/13 Update: We have re-released Azure DevOps Server 2022.2 to fix the loading Teams names issue. If you have installed the version of Azure DevOps Server 2022.2 released on July 9, you can install Patch 1 for Azure DevOps Server 2022.2 to fix the issue. Patch 1 is not required if you are installing Azure DevOps Server 2022.2 for the first time since the download links have been updated to include the fix. You can download Patch 1 from this link.

8/5 Update: We are currently testing a fix for the loading Teams names issue. We will continue sharing updates in this blog post and expect to announce a release date by the end of this week.

7/19 Update: The issue affecting Boards Team Configuration was successfully resolved with the Azure DevOps Server 2022.2 RTW release. We are still investigating the issue with loading Teams names and will continue to share updates in this blog.

7/16 Update: We are currently investigating issues with loading Boards Team Configuration and loading Teams names. You can use Security settings as a workaround to manage Team members.

We will share updates in this blog as we make progress investigating these issues.

Today, we released Azure DevOps Server 2022.2 RTW. This is our final release of Azure DevOps Server 2022.2 and will be the new supported version for the Azure DevOps Server 2022 server listing.

You can directly install Azure DevOps Server 2022 Update 2 or upgrade from any version of Azure DevOps or TFS, including Team Foundation Server 2015 and newer. You can find the full details in our release notes.

Here are some key links:

We’d love for you to install this release and provide any feedback at Developer Community.

Category
Azure DevOps ServerReleases

Author

Gloridel Morales
Gloridel Morales
Senior Technical Program Manager

Gloridel is a Senior Technical Program Manager on the Azure DevOps team.

38 comments

Newest
Newest Popular Oldest
  • Ninad Patil · Edited

    Hello Team,

    We are upgrading our Azure DevOps instance from v2022.1 to v2022.2

    While upgrading, we observed that Option for configuration of elastic search while upgrading instance is grayed out.

    We have reproduced this same senario on multiple instances we observed this same issue.

    May i request kindly check and let us know if its global issue on application upgrade v2022.2

    Thanks

  • Milan Kopáč

    I would like to ask why when we installed Azure DevOps Server 2022.2 from ISO with hash "010DDB7C750E7C1951186656FD8ABE2CA0DEAC5B232B85AE40DC737B08318E36" which should be Azure DevOps Server 2022.2 (based on: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2022-sha?view=azure-devops) we see this version of Azure DevOps Server 2022.2:
    Version Azure DevOps Server 2022.2 (AzureDevopsServer_20240806.7) 19.235.35206.7 (AzureDevOpsServer2022.2)
    Isn't the version 19.235.35206.7 with Patch 1? If so, why the Hash doesn't fit with Patch 1 in here: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2022-sha?view=azure-devops?

    Read more
    • Gloridel MoralesMicrosoft employee Author

      Correct, Azure DevOps Server 2022.2 ISO with hash “010DDB7C750E7C1951186656FD8ABE2CA0DEAC5B232B85AE40DC737B08318E36” includes fixes that we released with Patch 1.

    • Gloridel MoralesMicrosoft employee Author

      Hi Milan, we have two different builds one for the ISO and another build for Patch 1. This is why the versions don’t match between the two versions.

  • Bruce Farrar

    I would like to get further clarification expanding upon the comment from Markus below and the response from Gloridel. I would like to ask Gloridel again whether the ISO we download that has a a compile date of August 6, 2024 and internally has a version of 19.235.35206.7 is indeed the complete 2022.2 that has the Teams fix (from patch 1) integrated into it. If so, why does 2022.2 Patch 1 have an internal version...

    Read more
  • Markus

    Could you please provide a filehash to determinate which version has been downloaded.
    As versioning is only for beginners

  • Christian Hanna

    Hi Gloridel,

    please provide the link to download Patch1. Unfortunately, I cannot find it :/

    Thx & best regards,
    Christian

  • Robert Beaubien

    Hi Gloridel,

    I was wondering if you can point to a document regarding moving a repository from DevOps Server CPE complete with history to github. All the information I have been able to find is all out of date.

  • Markowitz, Steven · Edited

    Hi Gloridel,

    In reference to the issue involving editing team membership and administrator selection...

    https://developercommunity.visualstudio.com/t/Blank-page-when-accessing-Team-configura/10661411?q=team+configuration

    ... can you provide any updates on the progress of a correction and a ETA?

    If a correction is not going to be released soon are you recommending we proceed with using the 2022.2 RTW release for our production upgrade or should we continue waiting for a revised relesae to be issued?

    Thanks

    Steven

    Read more
  • Przemek Wirkus

    Please can you provide the link to the patch of issue affecting Boards Team Configuration? I downloaded the iso from you link and it has the same size as the ISO from 7/07/2024 download and files inside are from 2/07/2024. Release note page is from 16/07 and patch info is from 19/07.

    • Gloridel MoralesMicrosoft employee Author

      Hi Przemek, the issue affecting Boards Team Configuration was addressed in the RTW release. Yesterday we re-released Azure DevOps Server 2022.2 to include a fix for the loading Teams name issue. You can download the latest from our download page.

    • Carsten Krüger · Edited

      We are seeing the same problem.
      GitOdbStorageIntervalCleanupJob & GitAdvSecCommitScanningJob are piling up (nearly 4000 jobs queued and 8000 dormant)

      Result: Blocked

      Result Message: Re-queued job because there are too many concurrent jobs running.

      • Tore Østergaard Jensen (TORE) · Edited

        Didn’t even notice GitOdbStorageIntervalCleanupJob between all the GitAdvSecCommitScanningJob but we have that one too and also a single GitPushCIHandlerJob.

        I wonder if these jobs will eventuelle chew their way through their work and stop triggering that much – we are only 4 days away from the upgrade.

Read next