This month, we are releasing fixes that impact our self-hosted product, Azure DevOps Server.
The following will be fixed with this patch:
- Addressed issue that required restarting tfsjobagent service and Azure DevOps Server application pool after updating SMTP-related setting in the Azure DevOps Server Management Console.
- Copy Endpoint state to Service Endpoint edit panel instead of passing it by reference.
- Fixed in Notification SDK for when a team has notification delivery set to Do not deliver. In this scenario, if the notification subscription is configured with the Team preference delivery option, team members won’t receive the notifications.
Azure DevOps Server 2022 Patch 3
If you have Azure DevOps Server 2022, you should install Azure DevOps Server 2022 Patch 3. Check out the release notes for more details.
Verifying Installation
- Run
devops2022patch3.exe CheckInstall,devops2022patch3.exeis the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that it is not installed.
Good afternoon,
I have installed 2022 On Prem MS Server 2019. I installed Azure DevOps on the E drive and MS SQL 2019 on the D drive. When I attempted to install the Patches ( I tried all 3 of them ) I noted that in the install log “Could not find Patch in registry, no patches installed.”
Please advise
Thank you
I should have mentioned that I also have enabled the Search feature aka Elasticsearch.
Any help or advise would be greatly appreciated.
Correction the log states “Could not find Patch version in registry, no patches installed.” I did run the Check install and verified that no patches were installed.
Please disregard. The patch worked after repeated attempts to install. Things that make you go hmmm
Hi Gloridel
Thank you for the ongoing fixes!
Is it too early to ask for an estimated release date for 2022.1?
I also wonder if the Azure DevOps team is up for talks/collaboration during the upcoming Build conference?
Hi Tore, we are planning a minor release (2022.0.1) that will include bug fixes. The release candidate should be released within the next couple of weeks.
Hi Gloridel
That sounds nice!
We are specifically looking very much forward to Do not sync tags when fetching a Git repository, as our main repository has not been treated well and git seems unforgiving.
https://learn.microsoft.com/en-us/azure/devops/release-notes/2022/sprint-209-update?tabs=yaml#do-not-sync-tags-when-fetching-a-git-repository
Ok sounds like we have
I think that the wording is a bit different from Gloridel: “… that will include bug fixes.”.
Otherwise it wouldn’t be much different from the patches. So I am still hoping for some goodies – please, pretty please 🙂
+1 thanks for the continued support on the on-prem product.
Further to Tore’s question on 2022.1 ETA, it would be good to know what sprint you are targeting to bring the product up to. 218 to get all the board updates would be ideal.
This comment has been deleted.