Continuum as a Jenkins replacement? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 6 years ago.

Improve this question

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?).

Answer 1

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.