June 30th, 2020

Updated: Announcing Azure DevOps Server 2020 RC1

Gloridel Morales

Senior Technical Program Manager

Update: We received feedback in this blog and the Developer Community about an issue after upgrading from Azure DevOps Server 2019 Update 1.1 to Azure DevOps Server 2020 RC1. Today we are re-releasing Azure DevOps Server RC1 to fix this issue.

Previously, after upgrading from Azure DevOps Server 2019 Update 1.1 to Azure DevOps Server 2020 RC1 you were not able to view files in the Repos, Pipelines and Wiki of the Web UI. The error message indicated “an unexpected error has occurred within this region of the page. You can try reloading this component or refreshing the entire page.”

We identified a problem with a Feature Flag that comes with a different value when Azure DevOps Server is upgraded from Azure DevOps Server 2019 Update 1.1 to Azure DevOps Server 2020 RC1. The Feature Flag was created for Azure DevOps Server 2019 Update 1.1, and defaulted to On for that release. The intent of the Feature Flag was to address the memory issues in servers with low RAM by dropping all debug files. The fix with default to On for the Feature Flag was not ported to Azure DevOps Server 2020 RC1 release. In addition, we did not test the upgrade scenario with the default to On for Feature Flag in Azure DevOps Server 2020 RC1. We will add this and similar scenarios to our pre-release test coverage to avoid similar issues in the future. The fix is now available in Azure DevOps Server 2020 RC1 Patch 1 release.

If you have upgraded to the previous version of Azure DevOps Server 2020 RC1, we recommend that you upgrade to this new release. You can use the links provided below to upgrade from Team Foundation Server 2015 or newer, Azure DevOps Server 2019 and Azure DevOps Server 2020 RC1. We thank you for trying this release and reporting issue, and we apologize for the impact this may have caused.

We are very excited to announce Azure DevOps Server 2020 RC1. We’ve added a ton of new features which you can read about in our release notes. You’ll find a deeper dive into these great highlights, along with screenshots, samples and technical info to get you started.

Here are a few of the highlights:

This is a go-live release, meaning you can install it on production servers. We expect to have another RC release before our final release.

Here are some key links:

We’d love for you to install this release candidate and provide any feedback at Developer Community.

Author

Gloridel Morales

Senior Technical Program Manager

Gloridel is a Senior Technical Program Manager on the Azure DevOps team.

31 comments

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

Sort by :

Newest

Newest Popular Oldest

Scott Lezberg July 31, 2020 0

Is the “New Pull Request Experience for Azure Repos” part of ADO Server 2020? It does not seem to be even as an optional feature flag. This was introduced back in March (https://devblogs.microsoft.com/devops/introducing-the-new-pull-request-experience-for-azure-repos/comment-page-6/#comments) so was really hoping this would be part of ADO Server 2020 – any reason it is not?
Scott Lezberg July 21, 2020 0

I posted an collection upgrade issue in the developer community (https://developercommunity.visualstudio.com/content/problem/1098411/ado-2020-rc1-collection-upgrade-issue.html) but I am concerned it might not be getting the attention needed as we would want to make sure the collection upgrade scripts are solid . I am hoping ADO product management might see this comment and review the thread and see if we could work together to ensure this will be resolved in RC2. I can be reached at scottlezberg@deltek.com to work with anyone on this. Thanks
ws t July 15, 2020 0

This page (https://docs.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2020?view=azure-devops&branch=releasenotes%2FAzureDevOpsServer2020#wiki)
indicates that Mermaid is supported by the Wiki and shows an icon on the editing toolbar. This icon does not appear in my project’s wiki.
I confirmed the page code, “Wiki.Web.EnableMermaid” value is false.
How to set up to display the Mermaid icon?
- Gloridel Morales Author July 21, 2020 0
  
  Hi, Mermaid support is not included in the Azure DevOps Server, it is supported only in the Azure DevOps Service.
  - John Bown August 3, 2020 0
    
    Hi Gloridel,
    Use of mermaid diagrams is very important to us. We have set up wikis with extensive documentation and mermaid diagrams using Azure Devops Services ,and eagerly awaited upgrading to Azure Devops Server 2020 in order to bring them into our main on-premise server. Can you please clarify:
    Will mermaid diagram support ever be added to Azure DevOps Server? Was it omitted by error? Is it in the pipeline? Is there some licensing or technical issue that has prevented it from being included? Can you please elaborate on your reply.
    As I say, it is a very important feature...
    Read more
    Hi Gloridel,
    Use of mermaid diagrams is very important to us. We have set up wikis with extensive documentation and mermaid diagrams using Azure Devops Services ,and eagerly awaited upgrading to Azure Devops Server 2020 in order to bring them into our main on-premise server. Can you please clarify:
    Will mermaid diagram support ever be added to Azure DevOps Server? Was it omitted by error? Is it in the pipeline? Is there some licensing or technical issue that has prevented it from being included? Can you please elaborate on your reply.
    As I say, it is a very important feature to us, and a would prevent us using the DevOps wiki as our main development wiki.
    Other than that 2020RC1 is great.
    
    Read less
Maddison jams July 9, 2020 0

Thanks for sharing this blog, It’s really a well written and interesting piece. I also completed my assignment on DevOps. It is very helpful to me in DevOps. I have done learning this technology from the industry’s leader DevOps” and I believe your blog will help me. Thanks again.
Yasutomo Sugahara July 9, 2020 0

I was looking forward to the release.
Thank you for the good news!

I installed it immediately.
So I have one question.
Futures Time Line’s “Mermaid diagram support in wiki” doesn’t seem to be implemented. Is this postponed?
Or will it be implemented in the official release version?

This is the function we want most.
I would be very happy if you could include it in the official release.
- Gloridel Morales Author July 21, 2020 0
  
  Hi Yasutomo, Mermaid support is not included in the Azure DevOps Server, it is supported only in the Azure DevOps Service.
Aaron Hallberg July 6, 2020 0

Thanks to everyone who reported the issues with viewing code files, discussed in https://developercommunity.visualstudio.com/content/problem/1098066/azure-devops-server-2020-rc1-an-unexpected-error-h.html. A mitigation has now been posted in that problem report, and we are working on getting a fix out in an updated RC1 build. It should be noted that we believe the issue only impacts servers upgraded from Azure DevOps Server 2019 Update 1.1, which is why new installations and upgrades from other versions didn't experience the same problems. To those who did encounter the issue - our sincere apologies for the impact it had, and we will strive to learn from this incident and improve...
Read more
Thanks to everyone who reported the issues with viewing code files, discussed in https://developercommunity.visualstudio.com/content/problem/1098066/azure-devops-server-2020-rc1-an-unexpected-error-h.html. A mitigation has now been posted in that problem report, and we are working on getting a fix out in an updated RC1 build. It should be noted that we believe the issue only impacts servers upgraded from Azure DevOps Server 2019 Update 1.1, which is why new installations and upgrades from other versions didn’t experience the same problems. To those who did encounter the issue – our sincere apologies for the impact it had, and we will strive to learn from this incident and improve our processes for future releases.

@Kenneth Hutchins – Azure DevOps Server 2019 Update 1 had a bug that caused high memory consumption, and it sounds like you may be running into that. We released a fix in Azure DevOps Server 2019 Update 1.1 (discussed here: https://developercommunity.visualstudio.com/content/problem/705677/azure-devops-server-2019-high-memory-usage-after-i.html; available here: https://docs.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2019u1) that you should certainly install to see if it resolves your issue. That same fix will be included in Azure DevOps Server 2020.

@Danstur – “Go Live” means that the release is fully supported in production. That means a direct upgrade path will be provided to RTW, that customer support will engage with customers encountering issues, up to and including escalating to the product team’s on-call rotation, etc.

Thanks again to all who have tried out the release and provided feedback. And apologies again to everyone who ran into the issue viewing code files.

Read less
Daniel Sturm July 3, 2020 0

“This is a go-live release, meaning you can install it on production servers”
Well I mean nobody can stop me installing whatever version I want on our servers, the question is whether it’s a good idea.

So what does “go-live release” entail on Microsoft’s part? What is Microsoft’s commitment with regard to support, particularly with critical issues such as
https://developercommunity.visualstudio.com/content/problem/1098066/azure-devops-server-2020-rc1-an-unexpected-error-h.html ?
Kenneth Hutchins July 2, 2020 0

Thanks for the feedback. I was hoping to upgrade from Azure DevOps Server 2019.1 to 2020-RC-1 to resolve the memory consumption issue where Memory holds at 90-95%. But seems like there are issues with this release.

I will try to upgrade my test environment to 2020-RC-1 to see if it resolves our issue but how bad are these issues being reported?

Currently we use DevOps for the Repo/boards for version control and work collaboration.
Jorge Belenguer July 1, 2020 0

We were encouraged by this, and tried... but it is not ready so don't bother. Do not install in production servers as the article says.

We found the same issue as everyone else: files cannot be viewed/edited in the new version. This means no YAML pipeline creation/edition and no repository file inspection. Pretty big to me, not sure how that can escape QA.

I don't get how this can be considered RC in the first place, but also how it can be considered a "go-live" release. I hope this is corrected before anyone makes a big mistake.

Read more
We were encouraged by this, and tried… but it is not ready so don’t bother. Do not install in production servers as the article says.

We found the same issue as everyone else: files cannot be viewed/edited in the new version. This means no YAML pipeline creation/edition and no repository file inspection. Pretty big to me, not sure how that can escape QA.

I don’t get how this can be considered RC in the first place, but also how it can be considered a “go-live” release. I hope this is corrected before anyone makes a big mistake.

Read less
- Gloridel Morales Author July 2, 2020 0
  
  Hi Jorge, thank you for installing and providing your feedback. Did you submit your feedback in the Developer Community? This will help the correct team get your message and address the issue.
  - Jorge Belenguer July 2, 2020 0
    
    Hi Gloridel, I posted a couple of comments in an already existing post https://developercommunity.visualstudio.com/content/problem/1098066/azure-devops-server-2020-rc1-an-unexpected-error-h.html
    
    This issue is the only feedback about 2020 RC1 I can find there, which probably means it is happening to everyone who installed it. Looking forward for the fix.
  - Ed Glas July 4, 2020 0
    
    Hi @Jorge Belenguer, thank you for reporting this issue. This is a ship stopper class of issue, so once we are able to root cause it we will issue a fix on RC1.
    
    Note that as part of the release process we upgraded many live internal servers and did not see this issue, so it is definitely not happening on all servers. In this release we revamped the file explorer code to make it faster and cleaner. The new explorer has been live on the service for several months and we did not encounter this issue, so it is something specific...
    Read more
    Hi @Jorge Belenguer, thank you for reporting this issue. This is a ship stopper class of issue, so once we are able to root cause it we will issue a fix on RC1.
    
    Note that as part of the release process we upgraded many live internal servers and did not see this issue, so it is definitely not happening on all servers. In this release we revamped the file explorer code to make it faster and cleaner. The new explorer has been live on the service for several months and we did not encounter this issue, so it is something specific to the server. We will figure it out and get a fix out in a new RC1 release.
    
    Ed.
    
    Read less
Scott McNally July 1, 2020 0

Installed the product today, everything seems great except for editing a yaml pipeline. Only an error displays for that.

An unexpected error has occurred within this region of the page.
You can try reloading this component or refreshing the entire page.
Refresh page
Reload component
Error: monaco is not defined
Stack
in o
in f
in i
in h
in div
in div

ReferenceError: monaco is not defined
at serviceFactory.defineEditorTheme (ms.vss-features.monaco-editor.es6.EOSmRMqENx026Ee0.min.js:1)
at o.getEditorTheme (ms.vss-features.monaco-editor.es6.EOSmRMqENx026Ee0.min.js:1)Read more
Installed the product today, everything seems great except for editing a yaml pipeline. Only an error displays for that.

An unexpected error has occurred within this region of the page.
You can try reloading this component or refreshing the entire page.
Refresh page
Reload component
Error: monaco is not defined
Stack
in o
in f
in i
in h
in div
in div

ReferenceError: monaco is not defined
at serviceFactory.defineEditorTheme (ms.vss-features.monaco-editor.es6.EOSmRMqENx026Ee0.min.js:1)
at o.getEditorTheme (ms.vss-features.monaco-editor.es6.EOSmRMqENx026Ee0.min.js:1)
at o.getEditorOptions (ms.vss-features.monaco-editor.es6.EOSmRMqENx026Ee0.min.js:1)
at o.componentDidMount (ms.vss-features.monaco-editor.es6.EOSmRMqENx026Ee0.min.js:1)
at Jn (ms.vss-web.core-content.es6.nCtjs_VzHiWCElJ3.min.js:1)
at ms.vss-web.core-content.es6.nCtjs_VzHiWCElJ3.min.js:1
at unstable_runWithPriority (ms.vss-web.core-content.es6.nCtjs_VzHiWCElJ3.min.js:1)
at bt (ms.vss-web.core-content.es6.nCtjs_VzHiWCElJ3.min.js:1)
at Cr (ms.vss-web.core-content.es6.nCtjs_VzHiWCElJ3.min.js:1)
at mr (ms.vss-web.core-content.es6.nCtjs_VzHiWCElJ3.min.js:1)

Read less
- Gloridel Morales Author July 1, 2020 0
  
  Hi Scott, thank you for installing. Please provide your feedback at Developer Community so we can have the right team help you with this.