在本地TFS到VSTS的XAML构建迁移 [英] On Premises TFS to VSTS migration of XAML builds

问题描述

当前，我们在内部使用TFS 2017 Update 1，但我们必须在VSTS云平台上迁移TFS.此外，我们在使用自定义构建模板进行XAML构建的前提下TFS构建服务器.我们的问题是，在迁移之后，所有XAML构建定义都将照常工作吗?

Currently we are using TFS 2017 update 1 on premises but we have to Migrate TFS at VSTS cloud platform. Also we TFS Build Servers on premises having XAML builds using customized build template. Our problem is after migration all XAML build definition would working as usual or not?

当前，我们在内部使用TFS 2017更新1，但我们必须在VSTS云平台上迁移TFS.此外，我们在使用自定义构建模板进行XAML构建的前提下TFS构建服务器.我们的问题是，在迁移之后，所有XAML构建定义都将照常工作吗?

Currently we are using TFS 2017 update 1 on premises but we have to Migrate TFS at VSTS cloud platform. Also we TFS Build Servers on premises having XAML builds using customized build template. Our problem is after migration all XAML build definition would working as usual or not?

没有代码.我们是否需要重新配置所有构建服务器? 在VSTS上迁移之后，我们是否可以使用旧的所有XAML构建定义在本地配置所有构建服务器?

there is no code. Do we need to Re-configure all build server again? After migration on VSTS can we configure All build servers on premises as well using old all XAML build definitions or not?

请对此提出建议.

推荐答案

XAML构建在VSTS中不再可用，因此在迁移后它们将根本无法工作.

XAML builds are no longer available in VSTS, so they will not work at all after a migration.

好消息是TFS 2017支持内部版本vNext，因此您可以在迁移之前转换内部版本，以确保在迁移之后仍然可以进行构建.

The good news is that TFS 2017 supports build vNext so you can convert your builds before you migrate to make sure you can still build after the migration.

Build vNext(Azure DevOps Pipelines)比旧的XAML构建更加灵活，更易于设置和自定义.但是，如果您有很多自定义的版本，则可能需要一段时间才能将它们全部转换.

Build vNext (Azure DevOps Pipelines) are much more flexible and easier to set up and customise than the old XAML builds. However if you have a lot of customised builds then it might take a while to convert them all.

新构建系统的一大优势是，同一构建可以在多个分支中使用，这意味着您无需像在XAML系统中那样花太多的精力就可以进行构建转换每个分支.

One big advantage of the new build system is that the same build can be used across multiple branches, which might mean that you don't need to put as much effort in to converting builds as in the XAML system you needed a build per branch.

我的建议是，首先熟悉新的构建系统，并在迁移之前开始转换构建，然后再将TFS数据库导入VSTS.

My suggestion is that you begin by familiarise yourself with the new build system and start to convert the builds before you migrate, then you can import you TFS database in to VSTS.

这篇关于在本地TFS到VSTS的XAML构建迁移的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！