Continuum作为Jenkins替换？ [英] Continuum as a Jenkins replacement?

问题描述

在我们公司，我们正在对我们的Java开发/ QA街道的产品进行严格审查。我们正在寻找的产品之一是Apache Continuum。

有人可能有Continuum经验（最好是Jenkins经验）解释什么优点和缺点Apache Continuum是（特别是关于Jenkins）？

我的第一印象是：

优点：

• 更适合分组构建和项目（从UI角度）。

缺点：

• 没有清除信息中心。

解决方案 / div>

我们使用连续体，我们切换到jenkins。

Jenkins的优势：

• Findbug


• pmd


• checkstyle


• 代码覆盖率 emma ）


• 与神器集成


• 与< a href =http://www.sonarsource.org/>声纳


• 后期制作任务（构建其他项目，自动存档）
$ b $

• rpm / deb软件包（您可以每周使用yum / deb自动更新）
$ b $ b

在jenkins中，您可以创建视图，并且可以将项目分组。

At our company we're taking a critical look at the products in our Java Development/QA street. One of the products we're looking at is Apache Continuum.

Could someone with Continuum experience (and preferably also Jenkins experience) explain what the advantages and disadvantages of Apache Continuum are (especially with regards to Jenkins)?

My first impressions are:

Advantages:

• Better suited for grouping builds and projects (from a UI perspective).

Disadvantages:

• No clear dashboard.
• A relatively small community.
• No plugins (right?).

解决方案

We are using continuum and we switched to jenkins.

Jenkins advantages:

• Findbugs
• pmd
• checkstyle
• code coverage (very good chart see for emma)
• integration with artifactory
• integration with sonar
• post build task (build other projects, automatic archiving)
• new delivery of jenkins every week - critical bugs are solved very quickly
• rpm/deb packages (you can use yum/deb for automatic update every week)

In jenkins you create the view and you can group projects there.

这篇关于Continuum作为Jenkins替换？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！