Buildbot vs Go.CD

Buildbot vs Go.CD: What are the differences?

Developers describe Buildbot as "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. On the other hand, Go.CD is detailed as "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 Go.CD belong to "Continuous Integration" category of the tech stack.

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, Go.CD 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 Go.CD.

Buildbot and Go.CD are both open source tools. Go.CD with 4.98K GitHub stars and 789 forks on GitHub appears to be more popular than Buildbot with 3.98K GitHub stars and 1.36K GitHub forks.

According to the StackShare community, Go.CD has a broader approval, being mentioned in 27 company stacks & 6 developers stacks; compared to Buildbot, which is listed in 7 company stacks and 6 developer stacks.