Appveyor vs TeamCity

Get Advice Icon

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

Appveyor
Appveyor

100
77
+ 1
90
TeamCity
TeamCity

613
406
+ 1
254
Add tool

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.

- No public GitHub repository available -
- No public GitHub repository available -

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 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.
Get Advice Icon

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

Why do developers choose Appveyor?
Why do developers choose TeamCity?

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 TeamCity?
    Be the first to leave a con
    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

    What are some alternatives to Appveyor and TeamCity?
    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.
    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.
    GitLab CI
    GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
    See all alternatives
    Decisions about Appveyor and TeamCity
    No stack decisions found
    Interest over time
    Reviews of Appveyor and TeamCity
    Review ofAppveyorAppveyor

    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.

    How developers use Appveyor and TeamCity
    Avatar of DigitalPermits
    DigitalPermits uses TeamCityTeamCity

    TeamCity is our main continuous integration server. It starts creating builds and running tests based on commits that we make in our hosted bitbucket repositories. From there, we have a set of configuraitons that can deploy the built and tested artifacts (web app, batches, db, etc...) to a stage or production server. We still release manually, but we release often, and TeamCity has nice features to help us roll back when things don't work out as planned.

    Avatar of Stack Exchange
    Stack Exchange uses TeamCityTeamCity

    TeamCity builds then copies to each web tier via a powershell script. The steps for each server are:

    • Tell HAProxy to take the server out of rotation via a POST
    • Delay to let IIS finish current requests (~5 sec)
    • Stop the website (via the same PSSession for all the following)
    • Robocopy files
    • Start the website
    • Re-enable in HAProxy via another POST
    Avatar of Nate Ferrell
    Nate Ferrell uses AppveyorAppveyor

    We use AppVeyor for unit and integration testing of the Vaporshell module for Powershell, as well as deployment on successful tests via PSDeploy

    Avatar of Sascha Manns
    Sascha Manns uses TeamCityTeamCity

    I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.

    Avatar of Andrew King
    Andrew King uses TeamCityTeamCity

    Continuous integration for iOS apps.

    Avatar of Valery Sntx
    Valery Sntx uses AppveyorAppveyor

    Continious Integration

    Avatar of One Legal
    One Legal uses TeamCityTeamCity

    Build system.

    How much does Appveyor cost?
    How much does TeamCity cost?
    Pricing unavailable
    News about Appveyor
    More news