Appveyor vs Semaphore: What are the differences?
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; Semaphore: The continuous integration and delivery platform powering the world’s best engineering teams. Semaphore is the fastest continuous integration and delivery (CI/CD) platform on the market, powering the world’s best engineering teams.
Appveyor and Semaphore can be primarily classified 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, Semaphore provides the following key features:
- Docker, Kubernetes, iOS support & 100+ preinstalled Tools
- Customizable Continuous Delivery Pipelines
- Customizable Stages, Parallel Execution and Control Flow Switches
"Github integration" is the primary reason why developers consider Appveyor over the competitors, whereas "Easy setup" was stated as the key factor in picking Semaphore.
According to the StackShare community, Semaphore has a broader approval, being mentioned in 40 company stacks & 17 developers stacks; compared to Appveyor, which is listed in 19 company stacks and 16 developer stacks.
What is Appveyor?
What is Semaphore?
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 Semaphore?
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
When it comes to continuous Integration services, the choice is hard. There are several solutions available and it looks like the dev scene is very split. We've read and reviewed several solutions and we ended up making the choice between Codeship and Semaphore . Although Semaphore is used by slightly more developers, we've experienced a faster and easy flow using Codeship. Both do integrate Slack and GitHub very well, so this is not a point to set them apart. Both have a complex pricing system that is not that easy to calculate and predict. However, out in the wild, we found Codeship to have a better price point at heavy use.
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
The Bitbucket integration with branch whitelists allows you to conserve your 100 builds this month.
CI and Deploy (Ionic Viewer and Heroku)
master -> Deploy develop -> CI