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.
What is Appveyor?
What is Buildbot?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Appveyor?
What are the cons of using Buildbot?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I recommend using Travis CI and/or Appveyor in all projects.
Projects using these tools have given me confidence to know that I don't cause any breaking changes. Travis CI and Appveyor have functionality to test components of a project across multiple installation projects to ensure that modifications don't break a project. These tools integrate easily with GitHub and are useful in open source projects that must review contributions from many different people.
Appveyor, is awesome, it provides a lot of functionalities and a reduced price. If you want .NET CI, appveyor is the best option. Ever. Awesome support, easy configuration, private nuget repo included, many integrations, and useful documentation. The only downside is, sometime it's a little bit slow.
We use AppVeyor for unit and integration testing of the Vaporshell module for Powershell, as well as deployment on successful tests via PSDeploy