Appveyor vs Jenkins vs Travis CI

Get Advice Icon

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

Appveyor
Appveyor

100
77
+ 1
90
Jenkins
Jenkins

12.1K
9K
+ 1
2.1K
Travis CI
Travis CI

4.2K
2.9K
+ 1
1.7K
- 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 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.

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

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

Why do developers choose Appveyor?
Why do developers choose Jenkins?
Why do developers choose Travis CI?

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 Jenkins?
What are the cons of using Travis CI?
    Be the first to leave a con

    Sign up to add, upvote and see more consMake informed product decisions

    What companies use Appveyor?
    What companies use Jenkins?
    What companies use Travis CI?

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

    What tools integrate with Appveyor?
    What tools integrate with Jenkins?
    What tools integrate with Travis CI?

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

    What are some alternatives to Appveyor, Jenkins, and Travis CI?
    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.
    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.
    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.
    Bamboo
    Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
    See all alternatives
    Decisions about Appveyor, Jenkins, and Travis CI
    Jesus Dario Rivera Rubio
    Jesus Dario Rivera Rubio
    Telecomm Engineering at Netbeast · | 10 upvotes · 65.5K views
    atNetbeastNetbeast
    Mailjet
    Mailjet
    Intercom
    Intercom
    Amplitude
    Amplitude
    Firebase
    Firebase
    GitHub
    GitHub
    Bitrise
    Bitrise
    Travis CI
    Travis CI
    Objective-C
    Objective-C
    Android SDK
    Android SDK
    React Native
    React Native
    #End2end
    #SmartHome

    We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

    Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

    We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

    You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

    See more
    GitHub
    GitHub
    Appveyor
    Appveyor
    Travis CI
    Travis CI

    I recommend using Travis CI and/or Appveyor in all projects.

    Projects using these tools have given me confidence to know that I don't cause any breaking changes. Travis CI and Appveyor have functionality to test components of a project across multiple installation projects to ensure that modifications don't break a project. These tools integrate easily with GitHub and are useful in open source projects that must review contributions from many different people.

    See more
    Interest over time
    Reviews of Appveyor, Jenkins, and Travis CI
    Avatar of tschellenbach
    CEO at Stream
    Review ofTravis CITravis CI

    In the past we used to run Jenkins. The build server always had weird issues and was a pain to maintain. Travis is a great solution for CI. Their Debug build features makes it trivial to figure out why your build broke. The integration with Github is also very slick. One thing they could improve is the documentation on the .travis.yaml format. All in all, great company and very responsive supports. Over here at getstream.io we're a fan. Keep up the good work guys!

    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, Jenkins, and Travis CI
    Avatar of datapile
    datapile uses Travis CITravis CI

    Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.

    It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).

    Avatar of Kalibrr
    Kalibrr uses JenkinsJenkins

    All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.

    Avatar of Wirkn Inc.
    Wirkn Inc. uses JenkinsJenkins

    Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.

    Avatar of Bùi Thanh
    Bùi Thanh uses JenkinsJenkins
    • Continuous Deploy
    • Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
    • Staging and production stages: Build and rollback quicly with Ansistrano playbook
    • Sending messages of job results to Chatwork.
    Avatar of Pēteris Caune
    Pēteris Caune uses Travis CITravis CI

    While we usually run tests before commits, Travis goes further and tests with different Python versions and different database backends. It works great, and, best of all, it is free for open source projects.

    Avatar of AngeloR
    AngeloR uses JenkinsJenkins

    Currently serves as the location that our QA team builds various automated testing jobs.

    At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.

    Avatar of Trusted Shops GmbH
    Trusted Shops GmbH uses JenkinsJenkins

    We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.

    Avatar of Dieter Adriaenssens
    Dieter Adriaenssens uses Travis CITravis CI

    Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.

    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 Nate Ferrell
    Nate Ferrell uses Travis CITravis CI

    Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.

    Avatar of Andrew Williams
    Andrew Williams uses Travis CITravis CI

    To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel

    Avatar of Valery Sntx
    Valery Sntx uses AppveyorAppveyor

    Continious Integration

    How much does Appveyor cost?
    How much does Jenkins cost?
    How much does Travis CI cost?
    Pricing unavailable
    Pricing unavailable
    News about Appveyor
    More news