复制构建过程模板或重复使用现有的 [英] Copying build process template or reuse exsisting

问题描述

我想知道在设置新的TFS构建过程模板时要权衡些什么。
基本上，您有2个选项
-复制现有的xaml。本质上为当前团队项目创建模板的副本。
-使用现有的xaml。基本上是为多个团队项目共享相同的构建过程模板。

I am wondering what the tradeoffs are when setting en new TFS build process template. Basically you have 2 options - Copy existing xaml. Essentially creating a copy of the template for the current team project. - Use existing xaml. Essentially sharing the same build process template for multiple team projects.

我所说的屏幕是

The screen i am talking about

作为程序员，我会选择第二个选项，因此您只有一个定义点

As a programmer I would go for the second option so you have a single point of definition for the template greatly easing maintainability.

在我看来，折衷是
-单点定义，对于多个团队项目更容易维护
-多个定义，允许以独立的方式进行更改。

It seems to me the trade off is - Single point of definition, easier to maintain for multiple team projects - Multiple definitions, allowing for change in an independent manner.

我是否缺少某些东西，应该考虑一下还是应该简单地选择选项1 ？

Are there things i am missing and that i should be taking into consideration or should we simply go for option 1?

任何能帮助我做出此决定的最佳实践或现实生活经验将不胜感激。

Any best practices or real life experience that will help me make this decision would be greatly appreciated.

推荐答案

出于与您提到的可维护性相同的原因，我总是重复使用同一模板，这是最佳做法（不得有任何例外）。我为在构建定义之间变化的事物创建参数，以便轻松共享模板。

I always reuse the same template for the same reason you mentioned about maintainability and is a best practice(like anything there can be few exceptions). I create parameters for things that vary between the build definitions so that sharing the template is easy.

我过去在一个项目中工作过，我们为每个构建定义都创建了副本，当我们不得不更改某些内容时，这很痛苦。

I worked in a project in the past where we created copy for each build definition and it was painful when we had to change something.

这篇关于复制构建过程模板或重复使用现有的的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！