Appveyor vs Buildbot: What are the differences?

What is Appveyor? Continuous Integration and Deployment service for busy Windows developers. AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.

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.

Appveyor and Buildbot belong to "Continuous Integration" category of the tech stack.

Some of the features offered by Appveyor are:

• Scriptless, repetitive, one-click deployment of build artifacts to multiple environments
• YAML configuration
• Backed by Windows Azure platform

On the other hand, Buildbot provides the following key features:

• run builds on a variety of slave platforms
• arbitrary build process: handles projects using C, Python, whatever
• minimal host requirements: Python and Twisted

"Github integration" is the primary reason why developers consider Appveyor over the competitors, whereas "Highly configurable builds" was stated as the key factor in picking Buildbot.

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.

Trustpilot, Snipcart, and Exceptionless are some of the popular companies that use Appveyor, whereas Buildbot is used by Mozilla, Animoto, and Fetch Robotics. Appveyor has a broader approval, being mentioned in 19 company stacks & 16 developers stacks; compared to Buildbot, which is listed in 7 company stacks and 6 developer stacks.