Migrate assets from RM server to Team Foundation Server and Team Services
NOTICE - We have deprecated this tool. It will continue to serve as an open source sample solution.
As Bob,the Release Manager, I would like to migrate my assets from 2015 or 2013 U4 RM server to Visual Studio Team Foundation Server or Team Services, and start using the Release hub in Team Web Access.
What about TFS?
The release of Team Foundation Server 2015 Update 2, or higher, includes the new Release Management (RM) features. This solution targets Visual Studio Team Services and Team Foundation Server 2015 Update 2, or higher.
Customers have so far been interacting with RM Server using the WPF client, configuring the release templates and managing their pipelines using the XAML based workflow system. The new release management capabilities, that are available with VS Team Services and are going to be a part of TFS in a future version of TFS, are based on a light-weight workflow system.
The agent-based release templates authored using the WPF client used a set of fine-grained tasks that were available with the RM Server. The new workflow system does not provide all those tasks out of the box, making it harder to upgrade the templates to the new capabilities.
However, since both of them leverage Powershell heavily, it is possible to partially migrate the data from one to the other. This project aims to provide the guidance and tooling to help you with this migration.
Find out more
- Introduction to the Release Management service in Visual Studio Team Services
- Announcement: Moving from the earlier version of Release management service to the new one in Visual Studio Team Services
- Release Management for VSTS preview version
- Migrating Release Management 2013/2015 to Release Management Service
- Architecture differences between Release Management 2013 and Release Management 2015 and Release Management (RM vNext) for Visual Studio for Team Services
- Lab 1 - Using the RMWorkFlowMigrator to create release scripts
- Lab 2 - Using the resulting release scripts in a release pipeline
Collection of Information
We do not collect any personal information when you use the migration tool. When you use the migration tool with Internet connectivity, basic usage metrics is collected to help improve our products and services, and for statistical analysis. Consult the RM Workflow Migrator Guide for options of disabling the metrics collection at run-time.
Daniel Mann, Dave McKinstry, David Pitcher, Derrick Cawthon, Josh Garverick, Josh Sommer, Niel Zeeman, Richard Albrecht, Richard Fennell, Sergio Romero, Shashank Bansal, Shaun Mullis, Stawinski Fabio, Vladimir Gusarov, William Salazar
Notices for certain third party software included in this solution are provided here: Third Party Notice.
###Contribute Contributions to Print Cards are welcome. Here is how you can contribute to Print Cards:
- Submit bugs and help us verify fixes
- Submit pull requests for bug fixes and features and discuss existing proposals