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 toc:\Program Files\Azure DevOps Server 2020by 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 toc:\Program Files\Azure DevOps Server 2020by default. After installing Azure DevOps Server 2020.0.1 Patch 7, the version will be 18.170.31821.4.
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
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?
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.
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.
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.
I’m a bit confused about 2020.0.1 vs 2020.1.1
It says here that “Azure DevOps Server 2020.1 RTW is a roll up of bug fixes”.
So, is there a compelling reason to install 2020.1 over 2020.0? If so, what is the recommended upgrade path? I could imagine to first install 2020.0.1 Patch 7 and then install 2020.1.1 Patch 2?
Hi Twan, you don’t have to install Patch 7 before upgrading to 2020.1.1. You can upgrade to 2020.1.1 and then install Patch 2.
Blog post announcing Azure DevOps Server 2020.1.1
Hi @Gloridel,
I have scenario in which I want to have a connection between Azure DevOps Server and repositories on GitHub.com.
Where I can find documentation for it?
Hi Karol, are you wanting to connect Boards with a GitHub repository?
Hi @Gloridel,
I want to connect on-prem Azure DevOps Server Boards with GitHub.com (cloud version).
You have docs about cloud to cloud synchronization, but my scenario on-prem to cloud is not there.
Can you share with me documentation about how to configure azure devops server boards sync with github.com?
PS. My question is referring to your release notes:
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.Looking for the same.
More specific we’re looking on how to get the Azure DevOps board GitHub app to connect to our Azure DevOps server instance
@Gloridel
There is documentation on how to connect Azure DevOps boards services to GitHub.
I fail to find any documentation on how to connect Azure DevOps boards server to GitHub (SaaS).
can you point me in the right direction?
Hi Floris, you can find information in the Azure Boards-GitHub integration documentation.
Hi Gloridel
Thanks for that.
The documentation which you refer to states this:
”
On-premises Azure DevOps Servers support integration with GitHub Enterprise Server repositories.
“
The release notes of this patch state:
”
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.
“
So now I’m looking for configuring an integration between Azure DevOps server, and GitHub Enterprise Cloud.
I can’t find documentation specifically for this scenario.
Following the other documentation isn’t successful.
Do you know where I could find some documentation about connecting
– Azure DevOps server with GitHub Enterprise Cloud.
– or Azure DevOps server with GitHub.com
?
Thanks for all your help 🙂
Cheers
Floris
Hi,
Delivery Plans 2.0 is available for Azure DevOps Services. When can we expect it to available for Azure DevOps Server 2020.
I was hoping it would be released this year but early 2022 perhaps?
Hi Joakim, we expect to release Delivery Plans with our next major version of the product. Release date should be early 2022.
Installed Azure DevOps Server on-Premise 2020.0.1
InstallVersion 18.179.30910.2
Applied Patches
devops2020.0.1patch2, Version: 18.170.31123.3
devops2020.0.1patch3, Version: 18.170.31228.1
Program Version does not update in Program and Features or Help About:
Programs and Features: Azure Dev Ops Server 2020.0.1 Version: 18.170.30910.2
Azure Dev Ops Server Administration Console, Help, About: Azure Dev Ops Server 2020 (18.170.30910.2)
Is there a way to correct this for notification purposes or vulnerability scan reporting?
Is Azure DevOps Server on-Premise 2020.1 still in pre-Release or Release Candidate status? If so, when do you expect the official release of version 2020.1.1?
Azure DevOps 2020.1.1 was released in August:
https://devblogs.microsoft.com/devops/azure-devops-server-2020-1-1-rtw-now-available/
The latest Patch I have for my Team foundation server 2018 update 3.2 is in TFS Team Foundation Server 2018 Update 3.2 Patch 7. In order to apply patches, Do I need to update patches from Team Foundation Server 2018 Update 3.2 Patch 9 to Team Foundation Server 2018 Update 3.2 Patch 15 one by one? or is the latest patch is enough to cover all the vulnerabilities in TFS? What is the best approach?
Hi Satish, patches are cumulative. You can install Patch 15 without having to install previous patches one by one.
We’re currently on 18.170.30525.1 (Azure DevOps Server 2020) and noticed that one of our collections has significantly grown in size – backups of that collection are 38+ GB. Is there a tool / query that can help us find the projects(s) / objects that are consuming so much space? Would applying 2020.1.1 help?
We ended up installing Patch 2 for 2020.0.1 to solve an artifact retention problem:
https://developercommunity.visualstudio.com/t/Azure-DevOps-Server-2020-Retention-Polic/1306205
It did help for a while, but we have discovered a new problem that seems to (at least) partly arise from test results that are not deleted when their associated builds are. Updating to 2020.1.1 did not help and I have not been able to convince Microsoft that it is a general problem yet:
https://developercommunity.visualstudio.com/t/Test-runs-for-deleted-builds-are-not-del/1537665
This seems like the same problem: https://developercommunity.visualstudio.com/t/Automated-test-results-not-deleted-from/1489186
Often when we see this kind of database growth, it’s due to a combination of very large work items and many work item revisions. Do you have large custom fields for your user stories or bugs, and do they get updated a lot?
To confirm, check the size of your WorkItemLongTexts table.
Assuming my guess is correct, you can alleviate the problem by cloning older work items (which only copies the latest state) and then deleting the old version and then also deleting the old version from the recycle bin.
You can also try asking for help on the Developer Community site.
Hi Matt
Just a friendly comment: it sometimes feels like the effort used for reporting issues on Developer Community is wasted as you tend get them closed quite quickly as “Not a problem” or “Need more information”. That would be okay if it was feature requests. It feels like the Microsoft employees replying are not aware that Azure DevOps has an on-prem version, and when you explain, they asks you to try to install the latest version. This happens regardless if you already specified the latest version as being installed, but if it isn’t it would also be quite a big test to do on a production system.
Not possible to install…
Checking SOFTWARE\Microsoft\TeamFoundationServer\18.0 to see if Azure DevOps Server is installed
Found InstallPath: C:\Program Files\Azure DevOps Server 2020\
Found InstallVersion: 18.181.31527.1
Latest patch installed on machine is version 18.170.31003.2
Patch 18.181.31821.3 is the same or later version as the patch installed on machine, patch can be installed.
The Application Tier is configured.
The Search Tier is configured.
The Proxy Tier is not configured.
This patch does not apply to Azure DevOps Server version 18.181.31527.1.
Hit Enter to exit.
“Patch can be installed” and the version is higher than the installed version…. but “this patch does not apply”
any fixes for this?
Hi Jens, it looks like you are being impacted by the issue reported in this blog post.
Have seen a similar issue the past two patches. The CheckInstall option reports that the patch had not been applied but attempts to install results in:
Checking SOFTWARE\Microsoft\TeamFoundationServer\18.0 to see if Azure DevOps Server is installed
Found InstallPath: C:\Program Files\Azure DevOps Server 2020\
Found InstallVersion: 18.181.31527.1
Could not find Patch version in registry, no patches installed.
The Application Tier is configured.
The Search Tier is configured.
The Proxy Tier is not configured.
This patch does not apply to Azure DevOps Server version 18.181.31527.1.
Should add that this is a brand new Azure DevOps Server and patch 1 was the first patch that was attempted to be applied. Our old Azure DevOps Server was successful in applying Patch 1.
Hi Brian, it looks like you are being impacted by the issue reported in this blog post.
Our last patch installed is: devops2020.0.1patch1.exe. From then on there were 6 more patches. Do we need to installed every one of them separately?
And could you please explain, what is the difference between 2020.0.1 and 2020.1.1?
Thank you!
Hi Stavroula, you don’t need to install all patches separately. You can install patch 7 since patches are cumulative. Azure DevOps Server 2020.1.1 includes bug fixes to the Azure DevOps Server 2020.0.1 version. Check out the release notes for 2020.1.1 to learn about the fixes.