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:
- State transition restriction rules in Boards
- Stakeholders can now move work items across board columns
- Improve release security by restricting scope of access tokens
- Enhanced pull request experience
- Multi-repo triggers in Pipelines
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.
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!
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
Hi Magnus, we just released Azure DevOps Server 2020.1 RC2. We plan to release RTW early this summer.
Thanks for a great article
قیمت لامپ
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.
<code>
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?
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.