Team Foundation Build还是TeamCity？

本文介绍了Team Foundation Build还是TeamCity？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我们主要是MS商店，正在从事.NET LOB开发。我们还为我们的CRM应用程序使用了MS Dynamics ...所有开发人员当前都在使用VS / SQL Server2008。我们还使用VSS，但是每个人都讨厌它在工作，并且很快就会淘汰。

我们开始在整个团队中实施TDD的计划（〜ppp）。我已经安装了TeamCity，并使用2008 sln构建器以及使用由同事进行源代码控制分析的SVN成功运行了我的第一个自动化构建。当演示进行管理时，我认为他们开始购买我的蛇油，并抛弃了研究TFS的建议。

这使我对TDD体系结构的计划产生了影响；不过，以一种很好的方式，因为我一直认为TFS太昂贵了，对于我们的团队来说不值得（而且我在我曾经工作过的其他商店中也见过）。我确实觉得MS在TDD / CI领域落后了几年，而且第三方产品可能更好，更成熟了……我仍然需要做大量研究，但我认为我会来这里看看如果有人真的使用过这两个系统。问题，至少是故意的。 使用TFS / TFB代替TeamCity的实际利弊是什么-例如我们会失去/获得哪些好处？这里有没有人实际使用过这两个系统（用于TDD / CI的TFS和TeamCity / SVN）并且可以从实际角度发言？

我已经对此主题进行了一些搜索，而我在此处找到的一篇文章中提到，TFB的缺点是它仅支持MSBuild。我正计划在TeamCity中使用FinalBuilder。

感谢任何建议

EDIT：有没有人使用TFS作为其Build / CI服务器，并且可以讲述成功/失败的故事？

解决方案

我们是一家小型开发商店，因此决定Team Foundation Server对我们来说负担过多的开销。我们曾经编写自定义MSBuild脚本以从命令行运行，但是在发现TeamCity之后，我们将整个构建过程移到了它。

我们找到了TeamCity为了易于使用和配置，JetBrains提供了出色的支持和文档。与Microsoft相比，它们的发布和更新周期要快得多。

它们对SVN源代码控制的支持非常出色，我们喜欢它们同时支持MSTest和NUnit的事实。用于单元测试。

我们还喜欢TeamCity Professional版本是免费的，因此我们可以对其进行评估，以了解它是否对我们有用。我们尚未达到需要升级到企业版的项目配置数量（20）。

We are a mostly MS shop at work doing .NET LOB development. We also use MS Dynamics for our CRM app... all the devs are currently using VS/SQL Server 2008. We also use VSS, but everyone hates it at work and that is quickly on its way out.

We are begining our initiative for TDD implementation across the team (~dozen ppl). I've gotten TeamCity setup and have my first automated builds running succesfully using the 2008 sln builder and also using SVN that a co-worker had setup who is doing the source control analysis. When demoing to managament, I think they started to buy into my snake oil and threw out the suggestions of looking into TFS.

This threw a wrench in what I had planned for our TDD architecture; In a good way though, because I had always assumed that TFS was just too expensive and not worth it for our team (and i've seen the same in other shops i've worked at / know of). I do feel like MS is years behind in the TDD/CI area and that the third party products were probably much better and more mature... I still need to do a lot of research, but I figured I'd come here to see if anyone has actually used both systems.

I realize the TFS encompasses a lot more then just a build server... but I didn't want to make this too broad of a question at least on purpose. What are the practical pros/cons of using TFS/TFB instead of TeamCity - e.g. which benefits would we lose/gain? Has anyone here actually used both systems (TFS for TDD/CI and TeamCity/SVN) and can speak from practical standpoint?

I've done some searching on this topic, and one post I found here on SO mentioned that the cons of TFB was it only supported MSBuild. I was planning on using FinalBuilder with TeamCity; and it appears it also supports TFS as well...

Thanks for any advice

EDIT: Has anyone used TFS as their Build/CI server and can tell of success/failure stories?

解决方案

We are a small development shop, and decided that Team Foundation Server carries too much overhead for us. We used to write custom MSBuild scripts to run from the command line, but after we discovered TeamCity, we moved our entire build process over to it.

We've found TeamCity to be easy to use and configure, and JetBrains provides excellent support and documentation. They are also on a much faster release and update cycle than Microsoft.

Their support for SVN source control is excellent, and we like the fact that they support both MSTest and NUnit for unit testing.

We also liked the fact that the TeamCity Professional edition was free, so we could evaluate it to see if it worked for us. We haven't hit the number of project configurations (20) that would require us to upgrade to the Enterprise edition.