TFS 2008/2010 与 Jenkins 的持续集成 [英] TFS 2008/2010 vs Jenkins for Continuous Integration

问题描述

Does anyone have specific experiences with using TFS 2008/2010 AND Jenkins for Continuous Integration (CI)? We are trying to decide which CI server to use. Our team works exclusively in Microsoft .NET/Visual Studio 2010/C#. We have the following requirements:

1. Automatically build our web project on every checkin.
2. Run unit tests with each build.
3. Automatically deploy green builds to development and/or test environments.
4. Provide pretty reports.
5. Provide build/deployment notifications via email.

I realize that installing a tool won't necessarily give us this functionality out-of-the-box and that we will have to integrate with other tools like MSBuild to achieve this.

I'm looking for specific features that Jenkins has that TFS 2008/2010 does not or vice versa. Also which is easier to maintain, use, etc.

解决方案

I would highly recommend using Jenkins - it will do all of your requirements out of the box apart from possibly #3, but if you can script your deployments then it can do that as well.

Here are some links to help you get your builds up and running:

Blog about doing .NET builds in Jenkins

Jenkins Windows installers

Installing the Jenkins master and slaves as Windows services

Disclaimer: I have no experience with TFS, but I think open solutions are nearly always more flexible and extensible (and cheaper !) than proprietary products.

这篇关于TFS 2008/2010 与 Jenkins 的持续集成的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！