TFS的构建过程在哪里进行? [英] Where is the TFS build process going?
问题描述
在设计构建过程时，我很难确定最好的方法是什么.看来微软已经(再次)扭转了局面.
Im having a hard time figuring out what the best approach is when designing my build process. It seems Microsoft have turned things around (again).
我正在使用TFS 2015和Visual Studio2015.对于早期版本的TFS，我通常创建了自定义代码活动，然后将其插入到构建定义过程文件(xaml)中.我喜欢这种方法，因为它给了我极大的灵活性，并使我能够编写.NET类.我使用了这些指南: https://msdn.microsoft.com/zh-我们/library/dd647551(v=vs.120).aspx
I am using TFS 2015 and Visual Studio 2015. For earlier versions of TFS I have normally created custom code activities that I plug in to my build definition process file (xaml). I like this approach because it gives me great flexibility and enables me to code .NET classes. I used these guides: https://msdn.microsoft.com/en-us/library/dd647551(v=vs.120).aspx
在TFS 2015中，似乎没有有关如何创建自定义代码活动的文档.实际上，微软似乎已经改变了一切，现在专注于脚本语言而不是自定义.NET代码:
In TFS 2015 it seems that there is no documentation on how to create custom code activities. In fact, it seems that Microsoft have changed things and now focuses on scripting languages in stead of custom .NET code: https://msdn.microsoft.com/en-us/Library/vs/alm/Build/steps/index.
我创建了一个自定义代码活动，它似乎可以在TFS 2015中运行(有一些hack)，因此仍然可行，但是我很担心这种方法不再可行.
I have created a custom code activity and it seems to be working in TFS 2015 (with a few hacks) so it is still possible, but I am nervous that this approach is no longer the way to go.
任何人都可以提供有关这里发生的情况的信息吗?
Can anyone provide information about what is happening here?
推荐答案
TFS 2015引入了基于Web和脚本的，高度可定制的新版本.同时，TFS 2015将继续支持XAML Build模板和控制器.
TFS 2015 introduces new builds, which are web- and script-based, and highly customizable. Meanwhile, TFS 2015 will continue to support the XAML Build templates and controllers.
新版本基于不同的体系结构，并在完全不同的系统上运行.当前，您可以同时使用新版本和代理以及XAML版本，控制器和代理.
The new builds are based on a different architecture and run on a completely different system. Currently, you can use both the new builds and agents alongside your XAML builds, controllers, and agents.
我应该使用哪个版本?
如果您不熟悉Team Foundation Server(TFS)和Visual Studio Team Services，则应使用此新系统.大多数使用TFS和XAML构建经验的客户也将通过使用新系统获得更好的结果.
If you are new to Team Foundation Server (TFS) and Visual Studio Team Services, you should use this new system. Most customers with experience using TFS and XAML builds will also get better outcomes by using the new system.
新版本基于Web和脚本，并且高度可定制.它们留下了XAML构建的许多问题和局限性.例如，这个新系统包含了开发人员用来在其开发机器上构建代码的各种领域特定语言(DSL).我们希望这会减少遇到在我的机器上构建良好但在CI服务器上没有构建"问题的机会.
The new builds are web- and script-based, and highly customizable. They leave behind many of the problems and limitations of the XAML builds. For example, this new system embraces the diverse set of domain-specific languages (DSLs) that developers used to build the code on their dev machines. We expect this will reduce the chances of running into the "builds fine on my machine but not on the CI server" problem.
如果您具有大量自定义的XAML构建和自定义活动，则可以继续使用这些构建，直到准备好将业务逻辑移植到可以在新构建中运行的脚本中为止.
If you have heavily customized XAML builds and custom activities, you can continue using those builds until you are ready to port your business logic into scripts that can run in the new builds.
有用的文章供您参考:
- https://blogs.msdn.microsoft.com /visualstudioalm/2015/02/12/build-futures/
- https://msdn.microsoft.com/zh-cn/library/vs/alm/build/feature-overview
- https://blogs.msdn.microsoft.com/visualstudioalm/2015/02/12/build-futures/
- https://msdn.microsoft.com/en-us/library/vs/alm/build/feature-overview
这篇关于TFS的构建过程在哪里进行?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
