Continuum as a Jenkins replacement?

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

  • CruiseControl.NET and Git
  • Deploy Artifact From Jenkins to Archiva with NAnt
  • How to run jenkins as a different user
  • Remotely Track the Current Branch in Git
  • Jenkins + Cmake + JIRA = CI of multiple interdependent projects?
  • How to create concourse loop for repetitive resources and jobs?
  • My first impressions are:


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


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

  • How to make travis-ci work with a local git branch instead of a specific commit?
  • Sonar Adding a new project
  • How to access files in SVN using java
  • Clone git repository over ssh with username and password by Java
  • Hudson git plugin won't clone repo on Linux
  • How do I clone a job in jenkins?
  • One Solution collect form web for “Continuum as a Jenkins replacement?”

    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.

    Git Baby is a git and github fan, let's start git clone.