Now available: Azure DevOps Server 2019 Update 1, Release Candidate 2

Erin Dormier

Principal Program Manager

Today, we are announcing the release of Azure DevOps Server 2019 Update 1 RC2. This is our last planned prerelease before our final release of Azure DevOps Server 2019 Update 1. This second release candidate includes some bug fixes since RC1. You can upgrade from Azure DevOps Server 2019 Update 1 RC1 or previous versions of Azure DevOps Server or TFS. You can find the full details in our release notes.

Here are some key links:

We’d love for you to install this release candidate and provide any feedback via Twitter to @AzureDevOps or in our Developer Community.

Author

Erin Dormier

Principal Program Manager

19 comments

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

Jeff Bowman September 17, 2019

Hello Erin

Do you have a link to a feature roadmap for on-prem Azure DevOps Server? I’m finding this, but it’s for the hosted edition only:

https://docs.microsoft.com/en-us/azure/devops/release-notes/features-timeline

Thanks,
Jeff Bowman
Fairbanks, Alaska
- Erin Dormier Author September 17, 2019
  
  Hi Jeff,
  In the link you provided, if you look at the Server column, that is the version of on-prem that we expect the feature to be included.
Surendra Kolat August 18, 2019

@Erin Dormier, Do this release will have specific Data Migration Tool availbale. If no, which upcoming TFS release will have Data Migration tool which will be available for Migrating from TFS to Azure Devops Service.
- Erin Dormier Author August 19, 2019
  
  Hi Surendra,
  
  The final release of Azure DevOps Server 2019 Update 1 (expected by the end of August) will support the Data Migration Tool. However, it will be about three weeks after the release before it is supported.
  - Surendra Kolat August 21, 2019
    
    Thank you.
Scott Robertson August 13, 2019

Hi Erin,
Do you have a timeline for the final release of Azure DevOps Server 2019 Update 1? thanks.
- Erin Dormier Author August 13, 2019
  
  Hi Scott,
  
  We are planning to ship by the end of August.
  - Scott Robertson August 14, 2019
    
    Thanks Erin!
Manoj Mehta July 31, 2019

Hi Erin,
Apologies for posting here, but I don't know where to go next.
I run a small business - our web app and db is hosted on azure and dev through devops. The issue we have is in devops repo, the "Download as Zip" function is not working - as in it results in a corrupt archive each time. I reported this to azure support on July 1. Quick question: in terms of time taken to resolve this issue, what is the timeframe that flashes in your mind: a few hours? a couple of days maybe? If any of...
Read more
Hi Erin,
Apologies for posting here, but I don’t know where to go next.
I run a small business – our web app and db is hosted on azure and dev through devops. The issue we have is in devops repo, the “Download as Zip” function is not working – as in it results in a corrupt archive each time. I reported this to azure support on July 1. Quick question: in terms of time taken to resolve this issue, what is the timeframe that flashes in your mind: a few hours? a couple of days maybe? If any of these, you’d be way off mark – it’s been one month…and counting.
And that’s not all: I estimate I have spent about 15-18 hours on the phone with azure tech support. Simple math will tell you that is over 2 unproductive business days this month.
When your tech support in Mexico couldn’t resolve this issue initially, they referred the issue to Azure support HQ in California (as I understood). Since then Mexico relays suggestions received to and from Support HQ and each call goes like this: this time let’s try A, this time let’s try B, and so on. I have a call scheduled for today – email says we are going to try X this time. Of course.
I don’t understand two things: 1) why the problem of download repo files as zip is so complex to diagnose and resolve 2) when Mexico couldn’t solve the issue, why is azure relaying instructions/suggestions/experimentations via Mexico, instead of contacting me directly to quickly resolve the isue? Surely it’s not hard to imagine that each relay back and forth via Mexico takes a few days?
Maybe we are a start up with low volumes and we don’t fit in to Azure’s strategy, maybe >1 month is the Azure normal for problem resolution, the latter is alluded to by recent media reports: https://mspoweruser.com/microsoft-azure-continues-to-lag-behind-amazon-in-the-cloud-infrastructure-market/
Concluding by what I said in the beginning: I don’t know what to do.
Manoj
FudMe, Canada

Read less
- Erin Dormier Author August 1, 2019
  
  Hi Manoj,
  
  I just contacted our support team so we can get to the bottom of this. Could you mail me at egeaney@microsoft.com so we can run it down?