Wercker vs Concourse CI

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.

While in beta, Wercker offers unlimited free public and private repositories.

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.

Debugging on remote build agents is a nightmare (especially without isolated builds). Concourse CI can be run locally. When there are problems with the pipeline definition, it can be run and debugged locally. That means it takes less time to find and fix problems.

Resources are to Concourse as plugins are to Jenkins. In other words, resources allow Concourse CI to do just about any work necessary in a build. But resources follow a "service provider interface" that makes them easy to build in any language (not just JVM languages) and have a clearly defined computing model, built for composition. Resources don't clutter UI or tax performance.

BOSH is an open source tool for release engineering, deployment, lifecycle management, and monitoring of distributed systems. Since Concourse CI is built on top of BOSH, Concourse can scale across many servers or be run in the Cloud.

Build isolation keeps workers "clean". There's no configuration drift of agents. Or flaky interactions between build jobs.

Visual pipeline view makes it clear what the automation does. Simple navigation to logs makes it easy to understand what happened in a build.

Concourse defines three primitives that, together, can express arbitrary features and pipelines.