When comparing CloudBees vs Wercker, the Slant community recommends Wercker for most people. In the question“What are the best hosted continuous integration services?” Wercker is ranked 5th while CloudBees is ranked 8th. The most important reason people chose Wercker is:
Wercker is based on Docker and it allows developers to create their own deployment stacks inside Docker containers. These stacks range from programming languages, to services, and even to notifications.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Great enterprise level support
Quick access to experts who are responsive, helpful, and friendly.
Pro Private and internal SVN and Git repositories
Support for both SVN and Git private repositories.
Pro Highly customisable
Jenkins is by far the most customizable solution on the market. And CloudBees is built on Jenkins. There are over 400 plugins to support building and testing virtually any project.
Pro Free for open source projects
CloudBees offers a solution for owners and developers of free and open source projects to be hosted and built by their service.
Pro Ability to create and use custom environments
Wercker is based on Docker and it allows developers to create their own deployment stacks inside Docker containers. These stacks range from programming languages, to services, and even to notifications.
Pro Free unlimited number of private repositories CI while in Beta
While in beta, Wercker offers unlimited free public and private repositories.
Pro Social networking elements
Wercker has an activity feed with which different team members can see and follow everything their colleagues have been doing. This gives the tool a certain social network feel, much like GitHub itself.
Cons
Con Java-only solution (without plugins)
Jenkins supports only software built with Java (unless you use plugins)
