Appveyor vs Visual Studio Team Services

Overview

Appveyor

Stacks123

Followers131

Votes94

Azure DevOps

Stacks2.7K

Followers2.9K

Votes249

Appveyor vs Visual Studio Team Services: What are the differences?

Introduction:

When choosing between Appveyor and Visual Studio Team Services for your project's continuous integration and delivery needs, it's important to understand the key differences between these two popular tools.

Pricing Model: Appveyor typically offers a simpler pricing model with a set price per parallel build, making it a cost-effective option for smaller projects or teams with specific budget constraints. On the other hand, Visual Studio Team Services may offer more flexibility in pricing, especially for larger projects or enterprises with varying needs and resources.
Integration with Microsoft Ecosystem: Visual Studio Team Services seamlessly integrates with other Microsoft tools and services, such as Azure DevOps, GitHub, and Microsoft Teams, providing a cohesive development environment within the Microsoft ecosystem. While Appveyor can also integrate with various tools and services, its integration with the Microsoft ecosystem may not be as extensive or seamless.
Customization and Extensibility: Visual Studio Team Services offers a wide range of customization options and extensibility through its marketplace, allowing teams to tailor their CI/CD pipelines to specific requirements. Appveyor, while providing some degree of customization, may not offer the same level of flexibility and extensibility as Visual Studio Team Services.
Scalability and Enterprise Support: Visual Studio Team Services is well-suited for large enterprises and projects requiring advanced scalability and enterprise-level support, with features such as advanced security controls, compliance tools, and dedicated support options. Appveyor, while capable of handling projects of various sizes, may not provide the same level of scalability and enterprise support as Visual Studio Team Services.
Ease of Use and User Interface: Appveyor is known for its simplicity and user-friendly interface, making it a popular choice for teams looking for a straightforward CI/CD solution. Visual Studio Team Services, with its extensive features and capabilities, may have a steeper learning curve for new users, but offers a more comprehensive set of tools and functionalities once mastered.
Community and Support Resources: Visual Studio Team Services benefits from its large user community and comprehensive documentation, providing ample resources and support for troubleshooting, best practices, and knowledge sharing. While Appveyor also offers support resources and documentation, the breadth and depth of community engagement may not be as extensive as that of Visual Studio Team Services.

In Summary, understanding the key differences between Appveyor and Visual Studio Team Services in terms of pricing, integration, customization, scalability, user interface, and support resources can help you make an informed decision based on your project's specific requirements and constraints.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

Appveyor	Azure DevOps
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.	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.
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;	Agile Tools: kanban boards, backlogs, scrum boards; Reporting: dashboards, widgets, Power BI; Git: free private repositories, pull requests; Continuous Integration: automated builds and diagnostics; Cloud build agents: cross-platform agents for Windows, Mac and Linux; Testing Tools: unit testing, load testing, manual, exploratory and user acceptance testing; Release Management: automate deployments, gated approval workflows, audit trails; Marketplace: extensions for the Visual Studio family of products; Package Management: host npm and NuGet packages; IDE Support: Eclipse, IntelliJ, Xcode and Visual Studio; Integration: link code and releases to work items, builds, and test results
Statistics
Stacks 123	Stacks 2.7K
Followers 131	Followers 2.9K
Votes 94	Votes 249
Pros & Cons
Pros 20 Github integration 18 Simple, reliable & powerful 12 Hosted 11 YML-based configuration 10 Nuget support Cons 1 Complex user interface 1 Poor documentation	Pros 56 Complete and powerful 32 Huge extension ecosystem 27 Azure integration 26 Flexible and powerful 26 One Stop Shop For Build server, Project Mgt, CDCI Cons 8 Still dependant on C# for agents 5 Many in devops disregard MS altogether 5 Half Baked 4 Jack of all trades, master of none 4 Capacity across cross functional teams not visibile
Integrations
GitHub Bitbucket .NET	GitHub Visual Studio Docker Slack Trello Git IntelliJ IDEA Jenkins Octopus Deploy Eclipse

What are some alternatives to Appveyor, Azure DevOps?

Trello

Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process.

Jenkins

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.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

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.

Asana

Asana is the easiest way for teams to track their work. From tasks and projects to conversations and dashboards, Asana enables teams to move work from start to finish--and get results. Available at asana.com and on iOS & Android.

TeamCity

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.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Basecamp

Basecamp is a project management and group collaboration tool. The tool includes features for schedules, tasks, files, and messages.

Related Comparisons

Appveyor vs Visual Studio Team Services: What are the differences?

Introduction:

Pricing Model: Appveyor typically offers a simpler pricing model with a set price per parallel build, making it a cost-effective option for smaller projects or teams with specific budget constraints. On the other hand, Visual Studio Team Services may offer more flexibility in pricing, especially for larger projects or enterprises with varying needs and resources.
Integration with Microsoft Ecosystem: Visual Studio Team Services seamlessly integrates with other Microsoft tools and services, such as Azure DevOps, GitHub, and Microsoft Teams, providing a cohesive development environment within the Microsoft ecosystem. While Appveyor can also integrate with various tools and services, its integration with the Microsoft ecosystem may not be as extensive or seamless.
Customization and Extensibility: Visual Studio Team Services offers a wide range of customization options and extensibility through its marketplace, allowing teams to tailor their CI/CD pipelines to specific requirements. Appveyor, while providing some degree of customization, may not offer the same level of flexibility and extensibility as Visual Studio Team Services.
Scalability and Enterprise Support: Visual Studio Team Services is well-suited for large enterprises and projects requiring advanced scalability and enterprise-level support, with features such as advanced security controls, compliance tools, and dedicated support options. Appveyor, while capable of handling projects of various sizes, may not provide the same level of scalability and enterprise support as Visual Studio Team Services.
Ease of Use and User Interface: Appveyor is known for its simplicity and user-friendly interface, making it a popular choice for teams looking for a straightforward CI/CD solution. Visual Studio Team Services, with its extensive features and capabilities, may have a steeper learning curve for new users, but offers a more comprehensive set of tools and functionalities once mastered.
Community and Support Resources: Visual Studio Team Services benefits from its large user community and comprehensive documentation, providing ample resources and support for troubleshooting, best practices, and knowledge sharing. While Appveyor also offers support resources and documentation, the breadth and depth of community engagement may not be as extensive as that of Visual Studio Team Services.

Appveyor vs Visual Studio Team Services

Overview