April patches for Azure DevOps Server and Team Foundation Server

This post has been republished via RSS; it originally appeared at: Microsoft Developer Blogs.

This month, we are releasing patches that impact our self-hosted product, Azure DevOps Server 2019, as well as Team Foundation Server 2018. There are no security fixes with this patch; these patches include functional changes. The following has been fixed with this patch: SVN commits do not trigger pipeline Adding support for SHA2 in SSH on Azure DevOps Azure DevOps Server 2019.1.1 Patch 2 If you have Azure DevOps Server 2019 Update 1.1, you should install Azure DevOps Server 2019 Update 1.1 Patch 2. Verifying Installation Option 1: Run devops2019.1.1patch2.exe CheckInstall. devops2019.1.1patch2.exe is 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 is not installed. Option 2: Check the version of the following file: [INSTALL_DIR]\Azure DevOps Server 2019\Application Tier\Web Services\bin\Microsoft.VisualStudio.Services.Feed.Server.dll. Azure DevOps Server 2019 is installed to c:\Program Files\Azure DevOps Server 2019 by default. After installing Azure DevOps Server 2019.1.1 Patch 2, the version will be 17.153.3000.4. TFS 2018 Update 3.2 Patch 10 If you have TFS 2018 Update 2 or Update 3, you should first update to TFS 2018 Update 3.2. Once on Update 3.2, install TFS 2018 Update 3.2 Patch 10. Verifying Installation Option 1: Run tfs2018.3.2patch10.exe CheckInstall. tfs2018.3.2patch10.exe is 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 is not installed. Option 2: Check the version of the following file: [TFS_INSTALL_DIR]\Application Tier\Web Services\bin\Microsoft.TeamFoundation.WorkItemTracking.Web.dll. TFS 2018 is installed to c:\Program Files\Microsoft Team Foundation Server 2018 by default. After installing TFS 2018 Update 3.2 Patch 10, the version will be 16.131.30002.5.