What is Appveyor?
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.
Appveyor is a tool in the Continuous Integration category of a tech stack.
Who uses Appveyor?
27 companies reportedly use Appveyor in their tech stacks, including Trustpilot, Snipcart, and Blackfire.io.
80 developers on StackShare have stated that they use Appveyor.
GitHub, Bitbucket, .NET, SonarQube, and Octopus Deploy are some of the popular tools that integrate with Appveyor. Here's a list of all 8 tools that integrate with Appveyor.
Pros of Appveyor
- Scriptless, repetitive, one-click deployment of build artifacts to multiple environments
- YAML configuration
- Backed by Windows Azure platform
- Built-in NuGet feeds with project artifacts
- Build artifacts are stored in a highly-durable Geo-redundant cloud storage
Appveyor Alternatives & Comparisons
What are some alternatives to Appveyor?
See all alternatives
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.
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.
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.