Need advice about which tool to choose?Ask the StackShare community!
GoCD vs wercker: What are the differences?
GoCD: Open source continuous delivery tool allows for advanced workflow modeling and dependencies management. GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility; wercker: Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
GoCD and wercker belong to "Continuous Integration" category of the tech stack.
Some of the features offered by GoCD are:
- Model complex workflows with dependency management and parallel execution
- Easy to pass once-built binaries between stages
- Visibility into your end-to-end workflow. Track a change from commit to deploy at a glance
On the other hand, wercker provides the following key features:
- Pipelines - Wercker's Pipelines enable developers to fully automate builds, tests and deployments with Docker as a first class citizen.
- Workflows - With Workflows: a collection of pipelines can be chained and triggered to achieve complex automation goals.
- Steps Store - A step is a self contained best practice for accomplishing a specific automation task. Build your own or help yourself to our community based store.
"Open source" is the top reason why over 29 developers like GoCD, while over 34 developers mention "Automatic Deployments" as the leading cause for choosing wercker.
GoCD is an open source tool with 5.07K GitHub stars and 796 GitHub forks. Here's a link to GoCD's open source repository on GitHub.
FashionUnited, Hazeorid, and Wantedly are some of the popular companies that use wercker, whereas GoCD is used by Auto Trader, Hazeorid, and OpenX. wercker has a broader approval, being mentioned in 58 company stacks & 104 developers stacks; compared to GoCD, which is listed in 40 company stacks and 78 developer stacks.
I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.
Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.
Pros of GoCD
- Open source31
- Pipeline dependencies27
- Pipeline structures25
- Can run jobs in parallel22
- Very flexible20
- Plugin architecture15
- Environments can keep config secure13
- Great UI12
- Good user roles and permissions10
- Supports many material dependencies9
- Fan-in, Fan-out7
- Designed for cd not just ci6
- Empowers product people to make delivery decisions4
- Flexible & easy deployment2
- Pass around artifacts2
- Build once1
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 GoCD
- Lack of plugins2
- Horrible ui2
- No support1
