Need advice about which tool to choose?Ask the StackShare community!
Concourse vs wercker: What are the differences?
Developers describe Concourse as "Pipeline-based CI system written in Go". Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control. On the other hand, wercker is detailed as "Build, test, and deploy container-native applications". Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Concourse and wercker belong to "Continuous Integration" category of the tech stack.
"Real pipelines" is the top reason why over 8 developers like Concourse, while over 34 developers mention "Automatic Deployments" as the leading cause for choosing wercker.
Concourse is an open source tool with 3.99K GitHub stars and 482 GitHub forks. Here's a link to Concourse's open source repository on GitHub.
FashionUnited, Hazeorid, and DataHero are some of the popular companies that use wercker, whereas Concourse is used by DigitalOcean, Starbucks, and HelloFresh. wercker has a broader approval, being mentioned in 40 company stacks & 23 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.
I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !
I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.
We migrated all our CI/CD pipelines to CircleCI back in 2017 and are particularly happy about it since!
Our top loved feature is unlimited parallelism. We can run as many builds concurrently as we want.
We also use orbs, pipeline parameters, reusable commands, build cache, test insights.
For some of the heavier repos, we use a larger resource class and mount RAMdisk to a file system to speed up builds.
Pros of Concourse
- Real pipelines16
- Containerised builds10
- Flexible engine9
- Fast6
- Open source4
- No Snowflakes3
- Simple configuration management3
- You have to do everything2
- Fancy Visualization1
Pros of wercker
- Automatic Deployments35
- Free33
- Easy config via yaml25
- Awesome UI23
- Github integration23
- Continuous Deployment22
- Supports both Github and Bitbucket16
- Easy to setup14
- Reliable12
- Bitbucket Integration11
- Community-driven components (boxes and steps)4
- Fast builds4
- Easy to get started4
- Docker based4
- Easy UI3
- Flexible configuration via YAML3
- Multi-target deploys2
- Trigger by branch name1
- Great UI, free and an active Slack channel :)1
- Docker support1
- Multiple configurable build steps1
Sign up to add or upvote prosMake informed product decisions
Cons of Concourse
- Fail forward instead of rollback pattern2
