Java项目的Hudson和CruiseControl有什么区别？ [英] What is the difference between Hudson and CruiseControl for Java projects?

问题描述

我认为标题总结起来。我只是想知道为什么一个或另一个更好的连续集成构建的Java项目从Svn。

解决方案

时间CruiseControl提交者和从未使用过Hudson的人我很有偏见，但我的承诺是：

Hudson更容易启动和运行（大部分来自一个漂亮的网络界面），并有一个非常活跃的插件开发社区。

CruiseControl支持许多第三方的东西，并有一些整洁的技巧与插件预配置和包括xml配置的好处。项目，您可以通过项目版本配置信息。

如果你只有几个版本，我认为哈德森是明确的赢家。如果你要有很多 - 并不介意xml，那么我认为CruiseControl的xml配置技巧成为一个真正的实力。

I think the title sums it up. I just want to know why one or the other is better for continous integration builds of Java projects from Svn.

解决方案

As a long time CruiseControl committer and someone who has never used Hudson I'm pretty biased, but my take on it is:

Hudson is much easier to get up and running (in large part from a nice web interface) and has a very active plugin development community.

CruiseControl has support from lots of 3rd party stuff and has the benefit of doing some neat tricks with the xml configuration like plugin preconfiguration and include.projects which lets you version the configuration information with the project.

If you're only going to have a few builds I think Hudson is the clear winner. If you're going to have lots -- and don't mind the xml -- then I think CruiseControl's xml configuration tricks become a real strength.

这篇关于Java项目的Hudson和CruiseControl有什么区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！