Now available: Azure DevOps Server 2019 Update 1 RTW

Erin Dormier

Erin

Today, we are announcing the availability of Azure DevOps Server 2019 Update 1. Azure DevOps Server brings the Azure DevOps experience to self-hosted environments. Customers with strict requirements for compliance can run Azure DevOps Server on-premises and have full control over the underlying infrastructure.

This release includes a ton of new features, which you can see in our release notes, and rolls up the security patches that have been released for Azure DevOps Server 2019 and 2019.0.1. You can upgrade to Azure DevOps Server 2019 Update 1 from Azure DevOps Server 2019 or Team Foundation Server 2012 or later.

Here are some key links:

Here are some feature highlights:

Analytics extension no longer needed to use Analytics

Analytics is increasingly becoming an integral part of the Azure DevOps experience. It is an important capability for customers to help them make data driven decisions. For Update 1, we’re excited to announce that customers no longer need an extension to use Analytics. Customers can now enable Analytics inside the Project Collection Settings. New collections created in Update 1 and Azure DevOps Server 2019 collections with the Analytics extension installed that were upgraded will have Analytics enabled by default. You can find more about enabling Analytics in the documentation.

New Basic process

Some teams would like to get started quickly with a simple process template. The new Basic process provides three work item types (Epics, Issues, and Tasks) to plan and track your work.

Accept and execute on issues in GitHub while planning in Azure Boards

You can now link work items in Azure Boards with related issues in GitHub. Your team can continue accepting bug reports from users as issues within GitHub but relate and organize the team’s work overall in Azure Boards.

Pull Request improvements

We’ve added a bunch of new pull request features in Azure Repos. You can now automatically queue expired builds so PRs can autocomplete. We have added support for Fast-Forward and Semi-Linear merging when completing PRs. You can also filter by the target branch when searching for pull requests to make them easier to find.

Simplified YAML editing in Azure Pipelines

We continue to receive feedback asking to make it easier to edit YAML files for Azure Pipelines. In this release, we have added a web editor with IntelliSense to help you edit YAML files in the browser. We have also added a task assistant that supports most of the common task input types, such as pick lists and service connections.

Test result trend (Advanced) widget

The Test result trend (Advanced) widget displays a trend of your test results for your pipelines or across pipelines. You can use it to track the daily count of test, pass rate, and test duration.

Azure Artifacts improvements

This release has several improvements in Azure Artifacts, including support for Python Packages and upstream sources for Maven. Also, Maven, npm, and Python package types are now supported in Pipeline Releases.

Wiki features

There are several new features for the wiki, including permalinks for the wiki pages, @mention for users and groups, support for HTML tags, and markdown templates for formulas and videos. You can also include work item status in a wiki page and can follow pages to get notified when the page is edited, deleted or renamed.

Please provide any feedback via Twitter to @AzureDevOps or in our Developer Community.

23 comments

Comments are closed. Login to edit/delete your existing comments

  • Avatar
    Tony Gulino

    I’ve been waiting for the dark theme for a while. Thank you so much for working on it and including it with Update 1! It looks great, and will make my eyes very happy!

  • nikita egorov
    nikita egorov

    When do “Multi-stage YAML pipelines” come to the Azure DevOps Server?

  • Avatar
    Fred Zipperling

    Do you have a timeline on updating the Data Migration Tool to support Update 1?

  • Avatar
    Mathias Raacke

    Does the wiki now support “#” in page titles, so that I can create pages with titles like “C# coding conventions”?

  • Avatar
    Erik Berkun-Drevnig

    Will it ever be possible to use YAML pipelines with generic Git repos?

    • Erin Dormier
      Erin DormierMicrosoft employee

      Hi Erik,

      I just talked with our team and they said it is unlikely that we will isupport that scenario. There is way too much that is driven from what is inside YAML file, and it is hard to do that with any generic repo.

  • Surendra Kolat
    Surendra Kolat

    @Erin, Do we have compatiable Data Migration tool available for this release?

    • Erin Dormier
      Erin DormierMicrosoft employee

      Hi Daniel,

      Thanks for the feedback. I just added the build numbers to the feature timeline. Azure DevOps Server 2019 Update 1 is 17.153.29207.5.

    • Avatar
      Nick KirchemMicrosoft employee

      Hi Siavash, thanks for reporting this. This looks to be an issue in Update 1 with environments that use a network load balancer. We have a workaround for this, and we are fixing the issue in a forthcoming Update 1.1. You only need to apply the workaround once, and do not need to take any further action, even if you later install Update 1.1.
      You can run the following PowerShell on one of the Azure DevOps AT’s. This will add YOUR-FRONTEND-DOMAIN to the set of domains that the Azure DevOps server trusts. This is a one-time operation, and it only needs to be run once from any Application Tier (if you have multiple).
      [Reflection.Assembly]::LoadFrom(“C:\Program Files\Azure DevOps Server 2019\Tools\Microsoft.TeamFoundation.Client.dll”)$configServer = new-object Microsoft.TeamFoundation.Client.TfsConfigurationServer “https://YOUR-FRONTEND-DOMAIN”$configHive = $configServer.GetService([Microsoft.TeamFoundation.Framework.Client.ITeamFoundationRegistry])$configHive.SetValue(“/Configuration/WebSecurity/AllowedOrigins”, “YOUR-FRONTEND-DOMAIN,scheme=https;”)
      If you are using a non-default port (not 80 or 443) then you can add something like “,port=9081” to the entry above after scheme (but before the semi-colon). You can add multiple entries (if necessary) separated by the semi-colon.

      Thanks,
      –Nick

  • Avatar
    Cuadra, Ray

    Hi Erin,

    What is the best practice to apply this new version of Azure DevOps Server 2019? Do you first uninstall the current Azure DevOps 2019 version in your server? Or can you just launch the iso and it will perform the upgrade without issues?

  • Avatar
    Alexander Zimmermann

    Hi Erin,
    I’ve successfully upgraded DevOps from 2019.0.1 to Update 1, back in August.
    Beginning of this week we noticed that in the Boards->Process defined customization’s (added text fields, controls) have been gone.
    The data in old work items/bugs are still available, but in newly created work items/bugs the fields are not available.
    We just re-added them manually in the Boards->Process, no big deal.
    Is it possible that this could be from the upgrade? We are not sure why we realized it that late.

    Thanks Alexander

    • Avatar
      Linda HongMicrosoft employee

      Hi Alexander,

      It is unlikely that upgrading would cause this to happen. I suggest you check audit logs to see if anyone modified your process or reset fields.

      Thanks,
      Linda

      • Avatar
        Alexander Zimmermann

        Hi Linda,

        thank you for your answer!
        It seems like the Auditing feature is only available for DevOps Services?
        How can I access that kind of information on our DevOps Server?

        Thank you
        Alexander