如何在tfs 2013中与Service Fabric进行持续集成? [英] how to do continuous integration with service fabric with tfs 2013?

问题描述

存在大额有关如何为VSTS和 TFS 2015+ 创建构建定义的文档和示例的 a>用于Service Fabric的持续集成和部署.

There exists a great amount of documentation and samples on how to create build definitions for VSTS and TFS 2015+ for Service Fabric continuous integration and deployment.

与TFS 2013集成可用于部署Service Fabric应用程序的方面有哪些?

What is available in terms of integration with TFS 2013 for deployment of Service Fabric applications?

我们如何将本地Service Fabric群集/应用程序/服务的构建和部署与TFS 2013集成在一起?

推荐答案

Service Fabric是一个分布式系统平台，可以轻松打包，部署和管理可伸缩且可靠的分布式应用程序.它已开发了五年以上，仅作为Microsoft内部使用的平台，于 2015年作为产品公开发售.

Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable distributed applications. It was developed as a Microsoft-internal-only platform for over five years, which shipped publicly as a product in 2015.

vNext内部版本也于2015年发布，与XAML内部版本相比，具有许多好处，例如简单，深入的自定义.因此，大多数文档与vNext构建有关.

The vNext build is also released on 2015 and have many benefit such as simple, deep Customization than XAML build. So most documentation is related to vNext build.

根据 Azure资源管理器模板.您可以尝试使用Powershell来实现这一部分.最重要的是使用Powershell脚本发布到Service Fabric.

According to the build and release steps in documentation you provided above,it's general normal tasks such as build , test, copy files ,publish artifacts, it's not hard to convert to XAML build. You just need to do some build activities customization. One specific task is Azure Resource Group Deployment Task, there is no such correspondingly in XAML build. However, this task is used to create or update a resource group in Azure using the Azure Resource Manager templates. You could try to use powershell to achieve this part. The most import is using powershell script to publish to Service Fabric.

实际上，在使用TFS2013 XAML构建时，通常我们与Azure Cloud Service而不是Service Fabric集成.也有相关的博客，其中详细步骤显示了如何执行此操作.您可以参考:连续交付适用于Azure中的云服务

Actually, when working on TFS2013 XAML build, usually we integrate with Azure Cloud Service not service fabric. There are also related blog with detail steps show how to do it. You could take a reference: Continuous Delivery for Cloud Services in Azure

此外，由于您仍在使用XAML构建并保留在TFS2013上.我们鼓励您更新您的TFS版本以获取最新技术，并迁移到新的基于Web的vNext构建系统. 在TFS2018上，我们甚至删除了对XAML构建的支持 .为了获得VNext构建的好处，您可以参考本文:

Moreover, since you are still using XAML build and stay on TFS2013. We encourage you update your TFS version to get latest technology and move to new web-based vNext build system. On TFS2018, we even removed support for XAML Builds. For the benefit of VNext builds, you could refer to this article: Why You Should Switch to Build VNext

这篇关于如何在tfs 2013中与Service Fabric进行持续集成?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！