CI服务器的比较?

问题描述

我正在寻找不同的比较持续集成 (CI) 服务器(尤其是关注在 .NET 上)，但找不到任何内容.

I am searching for a comparison of different continuous integration (CI) Servers (esp. focusing on .NET) and couldn't find any.

因此，我想知道您对可用的不同解决方案，优缺点是什么，托管要求是什么以及为什么 CI Server XY 是您选择的服务器.

Therefore I'd like to know what you think about the different solutions available, what are the pros and cons, what are the hosting requirements and why CI Server XY is the Server of your choice.

我对您的想法很感兴趣(请随时发表评论其他人):

I am interested in your thoughts on (feel free to comment on others to):

• 哈德森
• CruiseControl
• CruiseControl.NET
• Teamcity
• CIFactory(使用 CruiseControl.NET)

兴趣点是:

• 配置(简单、灵活)
• 与 SCM 集成(尤其是 DSVC，如 git 或 hg)
• 与构建系统(MSBuild、NAnt、Rake)集成
• 与测试框架集成
• 与源分析(Simian、NDepend、FxCop、NCover 等)集成
• 网页界面/仪表板
• 基础设施要求

推荐答案

这样的问题没有大的链接是不完整的CI 特征矩阵(Web Archive) 列出了几乎所有的 CI 选项.

No question like this is complete without a link to the big CI Feature Matrix(Web Archive) which lists just about every CI option out there.

但我认为提前了解您希望在 CI 系统中包含的内容的范围很重要.它只是构建还是引入其他元素，如静态分析、跨项目依赖、部署、功能测试等.为了帮助进行规划，我在 企业 CI 元素(PDF；无需注册).请不要让E-word"让您失望；我只是指基本的快速反馈 CI 构建之外的东西.:)

But I think it is important to look ahead to the scope of what you want to include in your CI system. Is it going to be just builds or are you going to be bringing in other elements like static analysis, cross-project dependencies, deployments, functional tests, etc. To help with that planning I created this wallchart on the Elements of Enterprise CI (PDF; no registration required). Please don't let the "E-word" put you off; I just mean stuff beyond the basic fast feedback CI build. :)

它不是特定于工具的，但列出了您在规划/评估阶段可能会考虑的各种做法.

It isn't tool specific but lists a variety of practices you might consider while you're in the planning/evaluation stages.

这篇关于CI服务器的比较?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！