Need advice about which tool to choose?Ask the StackShare community!
Appveyor vs TeamCity: What are the differences?
Developers describe Appveyor as "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. On the other hand, TeamCity is detailed as "TeamCity is an ultimate Continuous Integration tool for professionals". 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.
Appveyor and TeamCity 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, TeamCity provides the following key features:
- Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
- Simplified setup: create projects from just a VCS repository URL
- Run multiple builds and tests under different configurations and platforms simultaneously
"Github integration" is the top reason why over 18 developers like Appveyor, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.
ebay, Intuit, and Apple are some of the popular companies that use TeamCity, whereas Appveyor is used by Exceptionless, Oconics, and Snipcart. TeamCity has a broader approval, being mentioned in 168 company stacks & 51 developers stacks; compared to Appveyor, which is listed in 19 company stacks and 16 developer stacks.
Pros of Appveyor
- Github integration20
- Simple, reliable & powerful18
- Hosted12
- YML-based configuration11
- Nuget support10
- Windows support6
- Free for open source4
- Automatic deployment4
- Great product, responsive people, free for open-source3
- Easy PowerShell support2
- Easy handling of secret keys2
- Remote Desktop into Build Worker1
- Advanced build workers available1
Pros of TeamCity
- Easy to configure61
- Reliable and high-quality37
- User friendly32
- On premise32
- Github integration32
- Great UI18
- Smart16
- Free for open source12
- Can run jobs in parallel12
- Crossplatform8
- Chain dependencies5
- Fully-functional out of the box5
- Great support by jetbrains4
- REST API4
- Projects hierarchy4
- 100+ plugins4
- Personal notifications3
- Free for small teams3
- Build templates3
- Per-project permissions3
- Upload build artifacts2
- Smart build failure analysis and tracking2
- Ide plugins2
- GitLab integration2
- Artifact dependencies2
- Official reliable support2
- Build progress messages promoting from running process2
- Repository-stored, full settings dsl with ide support1
- Built-in artifacts repository1
- Powerful build chains / pipelines1
- TeamCity Professional is FREE1
- High-Availability0
- Hosted internally0
Sign up to add or upvote prosMake informed product decisions
Cons of Appveyor
- Complex user interface1
- Poor documentation1
Cons of TeamCity
- High costs for more than three build agents3
- Proprietary2
- User-friendly2
- User friendly2
Sign up to add or upvote consMake informed product decisions
What is Appveyor?
What is TeamCity?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Appveyor?
What companies use TeamCity?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Appveyor?
What tools integrate with TeamCity?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+22
+46
+35