从用户的角度来看，Jenkins 和 Hudson 之间最显着的区别是什么? [英] What is the most notable difference between Jenkins and Hudson from an user perpective?

问题描述

Jenkins 从 Hudson 分道扬镳到现在大约 10 个月.

It is around 10 months now that Jenkins split off from Hudson.

查看项目主页时，我想知道 Hudson 和 Jenkins 之间的真正区别是什么.从变更日志中我并没有真正学到很多东西.有很多变化，主要区别似乎是 Jenkins 发布的频率更高，变化更少，而 Hudson 的发布频率更低，但版本中的变化更多.

When looking at the project homepages I am wondering what the differences between Hudson and Jenkins in the meantime really are. From the changelog I do not realy learn much. There are a bunch of changes and the major difference seems to be that Jenkins releases more often with less changes and Hudson less frequently, but then with more changes in a release.

还有什么明显的区别吗?那么，作为一名开发人员，是否有一些事情让我需要一个 CI 系统更有效率，而不是两者兼而有之?其中一个比另一个更稳定吗?是否有任何与甲骨文周围的政治无关的差异?

Are there any notable differences yet? So are there things that make me as a developer needing a CI system more productive rather with the one or the other? Is one of them more stable than the other? Is there any difference yet that has nothing to do with politics around Oracle?

在您看来，最显着的区别是什么?

What is the most notable difference from your point of view?

推荐答案

一个显着的区别是大量插件移至 Jenkins.虽然您仍然可以在 Hudson 中使用旧版本，但新版本已经依赖于 Jenkins.此外，新插件大多依赖于最近的 Jenkins 版本，因此您可能无法在 Hudson 上轻松使用它们.

One notable difference is that a big number of plugins moved to Jenkins. While you would still be able to use the old versions with Hudson, the newer versions depend on Jenkins already. Also new plugins are mostly created with dependencies on quite recent Jenkins versions, so you probably won't be able to use them without hassle on Hudson.

这可能会因插件而异，有些插件可能比其他插件更兼容 Hudson，而还有一些为这两种工具提供版本.但是，如果某个插件不能很好地工作，那么使用 Jenkins 会更容易获得帮助.

This will probably differ from plugin to plugin, some might be more compatible with Hudson than others, while still others provide versions for both tools. But if something does not work well with a plugin you will receive help easier if you use Jenkins.

这是我发现的 有趣的链接，不仅提供了一些可靠的Jenkins 和 Hudson 采取的不同路径上的数字，但也解决了此处另一篇文章中提到的(非)IP 问题......

Here is an interesting link I found, not only providing some solid numbers on the different paths Jenkins and Hudson have taken, but also addressing the (non-)issue of IP that was mentioned in the other post here...

这篇关于从用户的角度来看，Jenkins 和 Hudson 之间最显着的区别是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！