CI:Hudson with .Net vs CruiseControl.Net

CI: Hudson with .Net vs CruiseControl.Net(CI:Hudson with .Net vs CruiseControl.Net)

问题描述

我在一家希望集成 CI 服务器的 .net 商店工作.从我所见，Hudson 似乎是最受欢迎的选择.考虑到我们是一家仅限 .net 的商店，Hudson 会不会出现 CC.NET 不会遇到的任何障碍?

I work for a .net shop looking to integrate a CI server. From what I've seen, Hudson seems to be the most popular choice. Considering we are a .net only shop, will Hudson present any hurdles that CC.NET will not?

推荐答案

我想不出 Hudson 无法为我们的 C# 开发做的一件事，即使使用基于 MSTest 的测试，您现在也可以在它们上运行和绘制趋势图使用 新插件(仅在您测试 ONE 程序集时有效)或 我的方法 适用于多个程序集.

I cant think of a single thing that Hudson hasnt been able to do for our C# development, even with MSTest based tests, you can now run and trendgraph on them with the new plugin (only works if you are testing ONE assembly) or my method which works on multiple assemblies.

我想唯一好的做法是生成代码覆盖率数据并报告，但不确定 CC.net 是否这样做.

I suppose the only thing that would be nice, would be to generate code coverage data and report on that, not sure if CC.net does that.

此外，Hudson 似乎拥有更强大的社区支持.我从来没有听说过有人选择 CC.net 而不是 Hudson.

Also, Hudson seems to have much stronger community support. I've never heard of someone picking CC.net over Hudson if they had the choice.

我们用它来

• 部署 Windows 服务
• 部署网络服务
• 运行 MSTests &显示与任何 junit 测试一样多的信息
• 跟踪低、中、高任务
• 趋势图警告和错误

这些东西对 Hudson 来说可能不是什么新鲜事，但我觉得有必要再次强调，Hudson 可以通过 .net 项目处理这些问题，没问题.

These things may not be anything new to Hudson, but I felt the need to re emphasize that Hudson can handle this with a .net project, no problem.

以下是 Hudson 支持的一些内置 .net 内容

Here are some of the built in .net stuff that Hudson supports

• MSBuild
• NAnt
• MSTest(两种方法，上面链接)
• Nunit
• Team Foundation 服务器
• fxcop
• stylecop
• 编译器警告
• 编码任务

另外，上帝禁止你使用视觉源安全，它支持那也是.我建议你看看 Redsolo 的关于使用 Hudson 构建 .net 项目的文章

Also, god forbid you are using visual source safe, it supports that as well. I'd recommend you take a look at Redsolo's article on building .net projects using Hudson

这篇关于CI:Hudson with .Net vs CruiseControl.Net的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！