版本管理TFS 2015-无并行任务 [英] Release Management TFS 2015 - No Parallel Tasks

问题描述

我目前正在从站点发布管理的全部内容迁移到TFS 2015中的基于Web的版本.我注意到的一件事是，在旧客户端中，您可以创建部署序列并配置操作以并行运行，例如，我可能同时运行以下两个步骤:

I'm currently in the process of migrating from full fat on site Release Management to the web based version in TFS 2015. One thing I've noticed is that in the old client you can create a deployment sequence and configure actions to run in parallel, for example I might have these two steps running at the same time:

SQLServer-DeployDatabase.ps1
AppServer-DeployWebApp.ps1

SQLServer - DeployDatabase.ps1
AppServer - DeployWebApp.ps1

在基于Web的版本中，似乎只能串行设置动作"(现在称为任务")的等效项.因此，当您将并行任务的概念扩展到多个服务器角色(全部执行独立的步骤)时，您会发现可能会浪费大量时间.

In the web based version it appears the equivalent of 'Actions' (now being referred to as 'Tasks') can only be set serially. So you can see there's potentially a significant loss of time when you expand the idea of parallel tasks to multiple server roles (all performing independent steps).

为清楚起见，我知道您可以将任务设置为以一组服务器为目标，但这将使您一次只能运行一种类型的任务.

For clarity, I know you can setup a task to target a group of servers, but this will limit you to only running one type of task at a time.

所以我的问题是:此功能是否存在?我错过了某个地方的把戏吗?似乎新的基于Web的发布管理更加关注事物的并行环境部署方面，而忘记了在每个环境中尽可能快地进行部署的需求.

So my question is: Does this functionality exist? Have I missed a trick somewhere? It seems the new web based release management focuses more on the Parallel environment deployment aspect of things, forgetting the need to deploy in as fast a way as possible through each environment.

上面我所描述的例子.

An example of what I'm describing above.

并行模板

您可以看到在环境中，我在不同的服务器角色上进行了并行部署.我理解Daniel Mann在回答中提出的建议是创建多个环境并相应地触发，为此添加多个"Env"的问题是我们失去了所有好东西，例如快速复制和操作环境的能力. IE浏览器我设置了一个DEV环境模板并复制了这个环境"以创建"QA"，但是如果我有10个环境"作为一个真正的环境"，那么我就必须管理该开销.感觉到新产品中可能已删除了很大一部分可用性.还是我错过了新概念?

You can see that I have parallel deployments occurring on different server roles withing an environment. I understand the recommendation made in the answer by Daniel Mann is to create multiple environments and trigger accordingly, the problem with adding multiple "Envs" to cater for this is that we lose all of the good things like the ability to quickly copy and manipulate environments. IE I setup a DEV environment template and copy this one "environment" to create "QA", but if I had 10 "Environments" for one true "Environment" then I'd have to manage that overhead. It feels like a large chunk of usability may have been removed in the new offering. Or am I missing the new concept?

推荐答案

在这方面，TFS 2015中的产品有所限制，但此后一直在快速改进.在TFS 2017(和VS Team Services)中，可以为环境设置更健壮的环境触发器和部署条件.这使您可以扇出"到多个同时的环境，然后扇入"到后续环境.这样，您可以例如建立一个如下所示的环境管道:

The offering in TFS 2015 is a bit limited in that regard, but the offering has been improving rapidly since then. In TFS 2017 (and VS Team Services), you can set more robust environment triggers and deployment conditions for environments. This allows you to "fan out" to multiple simultaneous environments and then "fan in" to subsequent environments. With that, you can, for example, have an environment pipeline that looks like this:

         Dev
     _____|_________
     |              |
QA Database Tier QA Web Tier
     |_______________|
          |
       Staging
          |
         etc

只要有多个代理程序可以运行它们，两个"QA"环境都可以并行并行部署.

Both the "QA" environments could be independently deploying in parallel as long as there were multiple agents available to run them.

但是，还请记住，在TFS 2017和VS Team Services中，有关并行构建/部署的许可要求是不同的. TFS 2015中的发布中心被视为预览"，就可以运行多少个并行构建/部署管道而言，没有任何特定的许可要求.

However, also keep in mind that the licensing requirements around concurrent builds/deployments are different in TFS 2017 and VS Team Services. The Release hub in TFS 2015 was considered a "preview" and didn't have any particular licensing requirement in terms of how many concurrent build/deploy pipelines could be running.

这篇关于版本管理TFS 2015-无并行任务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！