Buildbot vs GoCD: What are the differences?
Buildbot: Python-based continuous integration testing framework. BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure; 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.
Buildbot and GoCD can be primarily classified as "Continuous Integration" tools.
Some of the features offered by Buildbot are:
- run builds on a variety of slave platforms
- arbitrary build process: handles projects using C, Python, whatever
- minimal host requirements: Python and Twisted
On the other hand, GoCD provides the following key features:
- 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
"Highly configurable builds" is the primary reason why developers consider Buildbot over the competitors, whereas "Open source" was stated as the key factor in picking GoCD.
Buildbot and GoCD are both open source tools. It seems that GoCD with 5.07K GitHub stars and 796 forks on GitHub has more adoption than Buildbot with 4.04K GitHub stars and 1.39K GitHub forks.
According to the StackShare community, GoCD has a broader approval, being mentioned in 40 company stacks & 78 developers stacks; compared to Buildbot, which is listed in 10 company stacks and 32 developer stacks.