Buildbot vs wercker: What are the differences?
What is 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.
What is wercker? Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Buildbot and wercker 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, 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.
"Highly configurable builds" is the primary reason why developers consider Buildbot over the competitors, whereas "Automatic Deployments" was stated as the key factor in picking wercker.
Buildbot is an open source tool with 4K GitHub stars and 1.37K GitHub forks. Here's a link to Buildbot's open source repository on GitHub.
According to the StackShare community, wercker has a broader approval, being mentioned in 40 company stacks & 23 developers stacks; compared to Buildbot, which is listed in 7 company stacks and 6 developer stacks.