Need advice about which tool to choose?Ask the StackShare community!

Appveyor

124
130
+ 1
94
Azure DevOps

2.7K
2.8K
+ 1
248
Add tool

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Appveyor
Pros of Azure DevOps
  • 20
    Github integration
  • 18
    Simple, reliable & powerful
  • 12
    Hosted
  • 11
    YML-based configuration
  • 10
    Nuget support
  • 6
    Windows support
  • 4
    Free for open source
  • 4
    Automatic deployment
  • 3
    Great product, responsive people, free for open-source
  • 2
    Easy PowerShell support
  • 2
    Easy handling of secret keys
  • 1
    Remote Desktop into Build Worker
  • 1
    Advanced build workers available
  • 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
  • 15
    Everything I need. Simple and intuitive UI
  • 13
    Support Open Source
  • 8
    Integrations
  • 7
    GitHub Integration
  • 6
    One 4 all
  • 6
    Cost free for Stakeholders
  • 6
    Project Mgmt Features
  • 5
    Crap
  • 5
    Runs in the cloud
  • 3
    Agent On-Premise(Linux - Windows)
  • 2
    Aws integration
  • 2
    Link Test Cases to Stories
  • 2
    Jenkins Integration
  • 1
    GCP Integration

Sign up to add or upvote prosMake informed product decisions

Cons of Appveyor
Cons of Azure DevOps
  • 1
    Complex user interface
  • 1
    Poor documentation
  • 8
    Still dependant on C# for agents
  • 5
    Many in devops disregard MS altogether
  • 4
    Capacity across cross functional teams not visibile
  • 4
    Not a requirements management tool
  • 4
    Half Baked
  • 3
    Jack of all trades, master of none
  • 3
    Poor Jenkins integration
  • 2
    Tedious for test plan/case creation

Sign up to add or upvote consMake informed product decisions

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.

What is Azure DevOps?

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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Appveyor?
What companies use Azure DevOps?
See which teams inside your own company are using Appveyor or Azure DevOps.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Appveyor?
What tools integrate with Azure DevOps?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Appveyor and Azure DevOps?
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.
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.
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.
GitLab
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.
Azure Pipelines
Fast builds with parallel jobs and test execution. Use container jobs to create consistent and reliable builds with the exact tools you need. Create new containers with ease and push them to any registry.
See all alternatives