Jenkins vs Travis CI comparison

You must select at least 2 products to compare!
Jenkins Logo
6,756 views|5,825 comparisons
88% willing to recommend
Travis CI Logo
639 views|779 comparisons
0% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Jenkins and Travis CI based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: May 2024).
771,968 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pricing and Cost Advice
  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    Information Not Available
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    771,968 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ask a question

    Earn 20 points

    out of 41 in Build Automation
    Average Words per Review
    out of 41 in Build Automation
    Average Words per Review
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 10% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Tekton logo
    Compared 6% of the time.
    Tekton logo
    Compared 61% of the time.
    GitLab logo
    Compared 18% of the time.
    TeamCity logo
    Compared 5% of the time.
    Learn More
    Travis CI
    Video Not Available

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    Easily sync your GitHub projects with Travis CI and you'll be testing your code in minutes. Travis CI for private repositories has plans for every size project. With Travis CI testing your open source project is 100% free.
    Sample Customers
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
    Top Industries
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    Financial Services Firm21%
    Computer Software Company17%
    Manufacturing Company11%
    Computer Software Company26%
    Financial Services Firm14%
    Healthcare Company8%
    Comms Service Provider8%
    Company Size
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Small Business17%
    Midsize Enterprise13%
    Large Enterprise70%
    Buyer's Guide
    Build Automation
    May 2024
    Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation. Updated: May 2024.
    771,968 professionals have used our research since 2012.

    Jenkins is ranked 2nd in Build Automation with 83 reviews while Travis CI is ranked 17th in Build Automation. Jenkins is rated 8.0, while Travis CI is rated 0.0. The top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". On the other hand, the top reviewer of Travis CI writes "Bamboo vs. Travis CI vs. Circle CI vs. Codeship". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Tekton, whereas Travis CI is most compared with Tekton, GitLab and TeamCity.

    See our list of best Build Automation vendors.

    We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.