Appveyor vs CircleCI vs Travis CI

Overview

CircleCI

Stacks14.5K

Followers7.1K

Votes974

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Appveyor

Stacks123

Followers131

Votes94

Appveyor vs CircleCI vs Travis CI: What are the differences?

Introduction: In the realm of continuous integration tools, Appveyor, CircleCI, and Travis CI are popular choices for automating build, test, and deployment processes. Each platform offers unique features and capabilities tailored to different project needs.

Integration with GitHub: Appveyor natively integrates with GitHub, allowing seamless setup and configuration with repositories. CircleCI and Travis CI also provide GitHub integration, but with slight variations in the setup process and functionality, making Appveyor a preferred choice for GitHub-centric projects.
Supported Platforms: CircleCI supports a wider range of platforms and operating systems compared to Appveyor and Travis CI. This broader support enables CircleCI users to build and test their projects on more diverse environments, catering to a variety of development needs.
Customizability and Flexibility: Travis CI offers more customization options in the build configuration compared to Appveyor and CircleCI. This level of flexibility allows users to fine-tune their build processes and incorporate specific requirements into their automation pipelines with greater control.
Ease of Use: Appveyor is known for its user-friendly interface and straightforward setup process, making it an excellent choice for beginners or teams with limited experience in continuous integration. On the other hand, CircleCI and Travis CI may require a steeper learning curve due to their more advanced features and configurations.
Parallel Builds: CircleCI excels in parallelization capabilities, enabling users to run multiple build jobs concurrently and optimize their build times significantly. This feature sets CircleCI apart from Appveyor and Travis CI, especially for projects that rely on fast feedback cycles and efficient testing processes.
Community and Support: Travis CI boasts a strong community of users and extensive documentation resources, making it easier for developers to troubleshoot issues and seek assistance when needed. While Appveyor and CircleCI also provide support channels, Travis CI's robust community presence enhances the overall user experience and knowledge-sharing opportunities.

In Summary, Appveyor, CircleCI, and Travis CI offer distinct advantages in terms of GitHub integration, platform support, customization, ease of use, parallel builds, and community support, catering to various project requirements and preferences.

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

Advice on CircleCI, Travis CI, Appveyor

Benjamin

CTO at NessPay

Feb 19, 2022

Decided

We chose github + github actions in order to manage the code versioning and the CI on the same software. Furthermore, while it is not that much, I believe that for a large team it is considerably cheaper to have one github subscription instead of a git subscription and a CI/CD software subscription.

281k views281k

Comments

Dustin

Senior Developer at Elegant Themes

Apr 18, 2019

Reviewon

CircleCI

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

607k views607k

Comments

Somnath

Engineering Leader at Altimetrik Corp.

Jun 25, 2020

Needs adviceon

CircleCI

Drone.io

GitHub Actions

I am in the process of evaluating CircleCI, Drone.io, and GitHub Actions to cover my #CI/ #CD needs. I would appreciate your advice on comparative study w.r.t. attributes like language-Inclusive support, code-base integration, performance, cost, maintenance, support, ease of use, ability to deal with big projects, etc. based on actual industry experience.

Thanks in advance!

1.82M views1.82M

Comments

Detailed Comparison

CircleCI	Travis CI	Appveyor
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.	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.	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.
Language-Inclusive Support;Custom Environments;Flexible Resource Allocation;SSH Or Local Builds For Easy Debugging;Improved Caching;Unmatched Security;Parallelism;Insights	Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.;Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.;Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.	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;
Statistics
Stacks 14.5K	Stacks 28.0K	Stacks 123
Followers 7.1K	Followers 6.7K	Followers 131
Votes 974	Votes 1.7K	Votes 94
Pros & Cons
Pros 226 Github integration 177 Easy setup 153 Fast builds 94 Competitively priced 74 Slack integration Cons 12 Unstable 6 Scammy pricing structure 0 Aggressive Github permissions	Pros 506 Github integration 388 Free for open source 271 Easy to get started 191 Nice interface 162 Automatic deployment Cons 8 Can't be hosted insternally 3 Feature lacking 3 Unstable 2 Incomplete documentation for all platforms	Pros 20 Github integration 18 Simple, reliable & powerful 12 Hosted 11 YML-based configuration 10 Nuget support Cons 1 Poor documentation 1 Complex user interface
Integrations
dotCloud GitHub Xcode Azure Container Service Slack Heroku JavaScript Node.js Python Amazon EC2	Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	GitHub Bitbucket .NET

What are some alternatives to CircleCI, Travis CI, Appveyor?

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.

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.

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.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Semaphore

Semaphore is the fastest continuous integration and delivery (CI/CD) platform on the market, powering the world’s best engineering teams.

Related Comparisons

Appveyor vs CircleCI vs Travis CI: What are the differences?

Integration with GitHub: Appveyor natively integrates with GitHub, allowing seamless setup and configuration with repositories. CircleCI and Travis CI also provide GitHub integration, but with slight variations in the setup process and functionality, making Appveyor a preferred choice for GitHub-centric projects.
Supported Platforms: CircleCI supports a wider range of platforms and operating systems compared to Appveyor and Travis CI. This broader support enables CircleCI users to build and test their projects on more diverse environments, catering to a variety of development needs.
Customizability and Flexibility: Travis CI offers more customization options in the build configuration compared to Appveyor and CircleCI. This level of flexibility allows users to fine-tune their build processes and incorporate specific requirements into their automation pipelines with greater control.
Ease of Use: Appveyor is known for its user-friendly interface and straightforward setup process, making it an excellent choice for beginners or teams with limited experience in continuous integration. On the other hand, CircleCI and Travis CI may require a steeper learning curve due to their more advanced features and configurations.
Parallel Builds: CircleCI excels in parallelization capabilities, enabling users to run multiple build jobs concurrently and optimize their build times significantly. This feature sets CircleCI apart from Appveyor and Travis CI, especially for projects that rely on fast feedback cycles and efficient testing processes.
Community and Support: Travis CI boasts a strong community of users and extensive documentation resources, making it easier for developers to troubleshoot issues and seek assistance when needed. While Appveyor and CircleCI also provide support channels, Travis CI's robust community presence enhances the overall user experience and knowledge-sharing opportunities.

Appveyor vs CircleCI vs Travis CI

Overview