Introducing Azure DevOps Server 2020.1 RC1

Gloridel Morales

Today we’re very excited to announce the first release candidate (RC) of Azure DevOps Server 2020.1!

We added many new features that you’ve been asking for. Here are a few of the highlights:

There are many more features with this release and you can read all about those features in our release notes. You can download Azure DevOps Server 2020.1 RC1 today. A direct upgrade to Azure DevOps Server is supported from any version of TFS, including Team Foundation Server 2015 and newer. Let us know any feedback or questions via the Developer Community.

Resources

22 comments

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

  • Daniel Steiner 0

    the release notes mentions an Optional Pre Upgrade Step and step 6 contains a link to github with the SQL script in a zip but the link is not valid.

    • Gloridel MoralesMicrosoft employee 0

      Hi Christian, the fix for the referenced bug will be included with the Azure DevOps Server 2020.1 RC2 release

  • Yury Volkov 0

    Hello!

    Can we expect Delivery Plans 2.0 (preview or not) to make an appearance in the update? Feature looks very hot. In fact so hot that we actually consider migrating task tracking to azure devops entirely.

    • Gloridel MoralesMicrosoft employee 0

      Hi Yury, Delivery Plans 2.0 will not be part of Azure DevOps Server 2020.1. We plan to release it with our next major release.

      • Yury Volkov 0

        Hi Gloridel. Major as in ADO 2021? That sounds like a long time away 🙁

      • Brat Yusuf 0

        thank you !

        • Brat Yusuf 0

          thank you !

  • Jonathan Gillette 0

    I attempted to run the script on our test ADO server, and got the following error:
    Online index operations can only be performed in Enterprise edition of SQL Server.

    Can I remove the ONLINE=ON option?

    • Tarun RamsinghaniMicrosoft employee 0

      Hi Jonathan,
      The step is optional and I’ll suggest that you can skip this step and proceed with the server upgrade as it will take care of this step as well.

      • Brat Yusuf 0

        thank you !

    • Gloridel MoralesMicrosoft employee 0

      Hi Jonathan, as Tarun mentioned the steps are optional. We removed them from the release notes to avoid confusion.

  • Tore Østergaard Jensen (TORE) 0

    Hi Gloridel

    Looking very much forward to the updates :-), but I have a few comments around my experience with Developer Community.

    Our biggest issue with 2020.0.1 currently is the broken retention policy on builds, so I would love to know if this is fixed in 2020.1:
    https://developercommunity2.visualstudio.com/t/Azure-DevOps-Server-2020-Retention-Polic/1306205
    https://developercommunity2.visualstudio.com/t/Collection-database-grown-from-15TB-to/1336215

    We have reported a lot of minor errors or inconveniences on our current install of 2020.0.1 RC, but we are getting kind of a cold shoulder on Developer Community asking us to use Azure DevOps Support instead, example:
    https://developercommunity2.visualstudio.com/t/ServicingJobData:DeleteProject/1351961

    Sometimes I am also getting suggestions form MSFT to run various manipulating queries against our collection database, in the follow case even a script from a fellow user:
    https://developercommunity2.visualstudio.com/t/MicrosoftTeamFoundationIdentity-unknow/1352013

    It seems that the Web UI gets less an less aware of regional settings and ‘just’ reacts on the browser language. This is not optimal for international workers (like us) that use English as our official corporate language, but still like to see date and time in a easily recognizable format:
    https://developercommunity2.visualstudio.com/t/User-time-and-date-format-should-be-resp/1322271

    • Gloridel MoralesMicrosoft employee 0

      Hi Tore, thank you for your continuous feedback. I will forward your comments about the Developer Community to the team. Regarding the retention policy bugs, they have been fixed in 2020.1

      • Tore Østergaard Jensen (TORE) 0

        Thank you!

        Looking very much forward to the retention policy fix 🙂

  • Jonathan Gillette 0

    I ran the upgrade yesterday on the test server, and it took 4h 32m to install. It spent 90% of the time in the Configure WCF step.

    [Info   @18:14:56.733] +-+-+-+-+-| Configure WCF |+-+-+-+-+-
    [Info   @18:14:56.737] Checking if the following feature(s) installed: WCF-HTTP-Activation45
    [Info   @18:14:56.738] Getting installed features...
    [Info   @18:34:56.812] Call cancelled 
    [Info   @18:34:56.815] Process starting: fileName=C:\Windows\system32\dism.exe arguments=/Online /NoRestart /Enable-Feature /FeatureName:WCF-HTTP-Activation45 /all
    [Info   @18:35:27.107] Waiting on process 2820 (30 seconds elapsed)
    [Info   @18:35:57.135] Waiting on process 2820 (60 seconds elapsed)
    ...
    [Info   @22:20:48.097] Waiting on process 2820 (13530 seconds elapsed)
    [Info   @22:21:10.550] Process finished: fileName=C:\Windows\system32\dism.exe arguments=/Online /NoRestart /Enable-Feature /FeatureName:WCF-HTTP-Activation45 /all exitCode=0 in 13573493 ms
    

    Using PowerShell’s Get-InstalledModule while it was in the middle of this, showed that WCF-HTTP-Activation45 was already installed. I’m assuming that something else caused it to not query properly?

    • Ross EskridgeMicrosoft employee 0

      Hi Jonathan,
      Based on your log snippet that time was entirely consumed by the Windows process installing a component requested by the upgrade, outside of the Azure DevOps Server process. That delay is almost certainly dependent on the state of your operating system, and not specific to the Azure DevOps Server upgrade.

  • diba irani 0

    Thanks for a great article

    قیمت لامپ

  • Magnus Timner 0

    Hi,
    I am looking forward to this release and have a question connected to the release date.

    I am working with a customer to migrate to Azure DevOps Service using the Microsoft migration tools. As that tools supports the latest and second latest version of Azure DevOps server and the customer is on Azure DevOps 2019.1 the release date of Azure DevOps 2020.1 is of interest.
    We are migrating the 14:th of May, do you think that Azure DevOps 2020.1 will be released before that date?

    Thanks
    Magnus

  • Ernesto Pye 0

    Hi Gloridel,

    Would this DevOps Server update include the ability to add suggested code changes in PRs, and then apply them directly from the web interface as seen here? https://devblogs.microsoft.com/devops/introducing-the-new-pull-request-experience-for-azure-repos/#add-suggested-changes-and-commit-within-a-pull-request

    Or would this be part of a following major release? We’re really excited about that feature and we’re eager to start planning the upgrade.

    Thank you!

Feedback usabilla icon