Appveyor vs Snap CI: 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 Snap CI? Build, test, and deploy software faster with Snap's continuous integration and deployment tool. Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.
Appveyor and Snap CI can be categorized as "Continuous Integration" tools.
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, Snap CI provides the following key features:
- Deployment Options - Heroku, AWS
- System Libraries - Your build runs on a RedHat 6-compatible system with commonly required libraries
- Customization Options - In addition to all that we support out of the box, we offer you the chance to customize your build extensively.
"Github integration" is the primary reason why developers consider Appveyor over the competitors, whereas "Github integration" was stated as the key factor in picking Snap CI.
According to the StackShare community, Appveyor has a broader approval, being mentioned in 19 company stacks & 16 developers stacks; compared to Snap CI, which is listed in 7 company stacks and 3 developer stacks.
What is Appveyor?
What is Snap CI?
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 Snap CI?
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.