Buildbot
Buildbot

42
44
+ 1
24
wercker
wercker

164
135
+ 1
242
Add tool

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.

- No public GitHub repository available -

What is Buildbot?

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?

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose Buildbot?
Why do developers choose wercker?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using Buildbot?
What are the cons of using wercker?
    Be the first to leave a con
      Be the first to leave a con
      What companies use Buildbot?
      What companies use wercker?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Buildbot?
      What tools integrate with wercker?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Buildbot and wercker?
      Jenkins
      In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
      TeamCity
      TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
      GitLab CI
      GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
      Bitbucket
      Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
      Travis CI
      Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
      See all alternatives
      Decisions about Buildbot and wercker
      No stack decisions found
      Interest over time
      Reviews of Buildbot and wercker
      No reviews found
      How developers use Buildbot and wercker
      Avatar of James Bowman
      James Bowman uses werckerwercker

      Automatic generation and deployment of site

      Avatar of Ruben Timmerman
      Ruben Timmerman uses werckerwercker

      For automated testing and deployment

      Avatar of WeeBull
      WeeBull uses BuildbotBuildbot

      Continuous Integration

      How much does Buildbot cost?
      How much does wercker cost?
      Pricing unavailable
      Pricing unavailable
      News about Buildbot
      More news
      News about wercker
      More news