October patches for Azure DevOps Server

Gloridel Morales

October 26th, 202134 1

This month, we are releasing fixes that impact our self-hosted product, Azure DevOps Server.

The following will be fixed with this patch:

  • Previously, Azure DevOps Server could only create connections to GitHub Enterprise Server. With this patch, project administrators can create connections between Azure DevOps Server and repositories on GitHub.com.
  • Resolve issue with Test Plan widget. The test execution report was showing an incorrect user on results.
  • Fix issue with the Project Overview summary page failing to load.
  • Fix issue with emails not being sent to confirm product upgrade.

Azure DevOps Server 2020.1.1 Patch 2

If you have Azure DevOps Server 2020.1.1, you should install Azure DevOps Server 2020.1.1 Patch 2. Check out the release notes for more details.

Verifying Installation

  • Option 1: Run devops2020.1.1patch2.exe CheckInstall, devops2020.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 2020\Application Tier\bin\Microsoft.Teamfoundation.Framework.Server.dll. Azure DevOps Server 2020.1.1 is installed to c:\Program Files\Azure DevOps Server 2020 by default. After installing Azure DevOps Server 2020.1.1 Patch 2, the version will be 18.181.31821.3.

Azure DevOps Server 2020.0.1 Patch 7

If you have Azure DevOps Server 2020.0.1, you should install Azure DevOps Server 2020.0.1 Patch 7. Check out the release notes for more details.

Verifying Installation

  • Option 1: Run devops2020.0.1patch7.exe CheckInstall, devops2020.0.1patch7.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 2020\Application Tier\bin\Microsoft.Teamfoundation.Framework.Server.dll. Azure DevOps Server 2020.1 is installed to c:\Program Files\Azure DevOps Server 2020 by default. After installing Azure DevOps Server 2020.0.1 Patch 7, the version will be 18.170.31821.4.

Gloridel Morales Senior Program Manager, Azure DevOps

Read next

34 comments

Discussion is closed. Login to edit/delete existing comments.

  • Matt Davis 0

    Hi Gloridel – Will there be a patch for Server 2020 that adds to support for builds targeting Visual Studio 2022? Or will that not come until Server 2022?

    • Tore Østergaard Jensen (TORE) 0

      I am wondering the same thing as I am fighting this problem right now.

      First, I had to set the VSTest capability to “C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TestWindow” in order to get the build started at all.

      Second, MSBuild@1 tasks cannot find VS 17 MSBuild.exe, but this can be specified as msbuildlocation to “C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\MSBuild.exe” on the task. However I would like to find a solution for this that I can apply as capability on the agent as this will be easier than fixing all MSBuild@1 calls.

      I wonder why the tasks are not made to leverage vswhere.exe correctly to also discover future Visual Studio releases. Right now the vswhere.exe is called with ranges so even though it can find VS 2022 it is ignored by the task.

      • Matt Davis 0

        If you are feeling adventurous, the steps for compiling and installing an updated version of the build task that includes it are on this stackoverflow link. Personally I would wait, since it isn’t clear to me how this will behave once the build task update is actually rolled out.

        https://stackoverflow.com/questions/70174595/visual-studio-2022-not-listed-in-devops-build-solution-pipeline-task

        In the future, it would be awesome if the GA release of Visual Studio could have a closely accompanying Server patch that adds the updates.

        • Tore Østergaard Jensen (TORE) 0

          I think I will wait too, to avoid other issues. However, I still wonder why it is needed when vswhere.exe seems to be forward compatible.

  • Twan Jacobs 0

    Hi Gloridel,

    While the release notes for Patch 7 specifically state “Fix issue with the Project Overview summary page failing to load”, we noticed that for us, with this patch applied, the summary page now remains empty. Clicking the summary tab results in a loading animation, but does not do anything else.

    In Chrome I see the server is missing a js file: /_static/_ext/ms.vss-tfs-web/project-overview-content/ms.vss-tfs-web.project-overview-content.es6.gl9mosG55Iyv3Vze.min.js

    Any ideas?

    Kind regards,
    Twan

Feedback usabilla icon