Updated: Azure DevOps Server 2022.2 RTW now available
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.
31 comments
Could you please provide a filehash to determinate which version has been downloaded.
As versioning is only for beginners
Hi Markus, you can find the file hashes for Azure DevOps Server 2022.2 in this document.
Hi Gloridel,
please provide the link to download Patch1. Unfortunately, I cannot find it :/
Thx & best regards,
Christian
Hi Christian, the link is in the release notes. You can download here. I have also updated the blog to include the link to the patch.
Release notes
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.
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
Hi Steven, the loading Teams name has been fixed.
I have updated this blog post and the release notes with details.
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.
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.
After upgrading we are now seeing the GitAdvSecCommitScanningJob blocked – not sure if it impacts something, but it does at least clutter the Azure DevOps Monitoring.
Has anyone else seen this?
Reported here:
https://developercommunity.visualstudio.com/t/GitAdvSecCommitScanningJob-blocked/10709401
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.
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.
Hi Gloridel,
Please could you help us out with a bug in Visual Studio TFS tools – https://developercommunity.visualstudio.com/t/Azure-DevOps-Error—0x00-is-an-inval/10603645
It is getting closed by there is a bug introduced in some middle release of VS2022 17.9+ that breaks editing XAML builds.
2022.2 is broken.
It’s not possible to manage teams.
If you click on: Project Settings – Teams – Team Name
nothing happens and an exception occurs in the browser console.
It happens only for teams which have a team admin set, teams without team admin could be opened.
Hi Carsten, the loading Teams name has been fixed.
I have updated this blog post with details.
Thank you Carsten for reporting this issue. We are currently investigating this issue and will share updates in this blog. In the meantime, you can use Security settings as a workaround to manage Team members.
Not sure if this is the same issue (since the update in the blog is described more as “loading Teams names” but its more than that) but after upgrading our test environment to 2022.2 RTW, I am not able to get to any of our Teams Profile pages (directly by clicking on the Team or indirectly trying to specify direct URL) for any of our projects (large or small and with and without team administrators). I do see these console errors.
This issue needs to be reopened – https://developercommunity.visualstudio.com/t/Blank-page-when-accessing-Team-configura/10661411?q=team+configuration&viewtype=solutions
Thanks
Scott
That workaround works for administering Team Members, but to my knowledge unfortunately not for administering Team Administrators.
We’re seeing the same thing in our test instance under the URI /Collection/Project/_settings/teams?teamId=d83c1564-591a-4700-af29-faa7c20917fc&__rt=fps&__ver=2.
Noticed the following errors showing up in the Event Logs:
1.Equals(T x, T y) at System.Collections.Generic.List
1.Contains(T item) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.CheckForCircularReference(JsonWriter writer, Object value, JsonProperty property, JsonContract contract, JsonContainerContract containerContract, JsonProperty containerProperty) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.CalculatePropertyValues(JsonWriter writer, Object value, JsonContainerContract contract, JsonProperty member, JsonProperty property, JsonContract& memberContract, Object& memberValue) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeList(JsonWriter writer, IEnumerable values, JsonArrayContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType) at Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType) at Newtonsoft.Json.JsonConvert.SerializeObjectInternal(Object value, Type type, JsonSerializer jsonSerializer) at Microsoft.TeamFoundation.Server.WebAccess.Admin.PlugIns.ProjectAdminViewDataProvider.GetData(IVssRequestContext requestContext, DataProviderContext providerContext, Contribution contribution) at Microsoft.VisualStudio.Services.ExtensionManagement.Sdk.Server.ExtensionDataProviderService.GetDataProviderData(IVssRequestContext requestContext, DataProviderContext providerContext, IEnumerable`1 dataProviderContributions, IDataProviderScope scope, Boolean executeClientProviders, Boolean executeRemoteProviders, Boolean userFriendlySerialization)Hi Gloridel. Can you elaborate more on the following statement?
This is our final release of Azure DevOps Server 2022.2
I am hoping that there are new versions like Azure DevOps Server 2023 or Azure DevOps Server 2024 coming up in the future, it’s just only that this last release under 2022 listing?
Hi Vasant, as Jonathan mentioned it is the wording that we use when publish the final build for an on-prem release.
That’s how they word it when the move from the RC to RTW. See 2022.1
https://devblogs.microsoft.com/devops/azure-devops-server-2022-1-rtw-now-available/