CircleCI vs TeamCity vs Travis CI comparison

Cancel
You must select at least 2 products to compare!
CircleCI Logo
1,878 views|1,711 comparisons
66% willing to recommend
JetBrains Logo
3,373 views|2,977 comparisons
92% willing to recommend
Travis CI Logo
631 views|774 comparisons
0% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between CircleCI, TeamCity, and Travis CI based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: April 2024).
768,578 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
  • "The price of CircleCI could be less expensive."
  • More CircleCI Pricing and Cost Advice →

  • "Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
  • "The licensing is on an annual basis."
  • More TeamCity Pricing and Cost Advice →

    Information Not Available
    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    768,578 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:The solution offers continuous integration and continuous delivery.
    Top Answer:Beware of skyrocketing bills as CircleCI does not provide transparency into how they charge refills. Their monthly… more »
    Top Answer:We've had occasional connectivity issues with cloud resources and build failure due to its own internal system setup and… more »
    Top Answer:TeamCity is a very user-friendly tool.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without… more »
    Top Answer:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it… more »
    Ask a question

    Earn 20 points

    Ranking
    11th
    out of 41 in Build Automation
    Views
    1,878
    Comparisons
    1,711
    Reviews
    2
    Average Words per Review
    342
    Rating
    4.0
    6th
    out of 41 in Build Automation
    Views
    3,373
    Comparisons
    2,977
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    17th
    out of 41 in Build Automation
    Views
    631
    Comparisons
    774
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    Comparisons
    Tekton logo
    Compared 21% of the time.
    Jenkins logo
    Compared 10% of the time.
    GitHub Actions logo
    Compared 8% of the time.
    AWS CodeBuild logo
    Compared 6% of the time.
    GoCD logo
    Compared 4% of the time.
    GitLab logo
    Compared 44% of the time.
    Jenkins logo
    Compared 9% of the time.
    Harness logo
    Compared 6% of the time.
    Tekton logo
    Compared 6% of the time.
    JFrog Pipeline logo
    Compared 1% of the time.
    Tekton logo
    Compared 60% of the time.
    GitLab logo
    Compared 18% of the time.
    Jenkins logo
    Compared 16% of the time.
    Learn More
    Travis CI
    Video Not Available
    Overview
    CircleCI's continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. CircleCI offers a modern software development platform that lets teams ramp quickly, scale easily, and build confidently every day.

    TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

    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
    Shopify, Zenefits, Concur Technologies, CyberAgent
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
    Top Industries
    VISITORS READING REVIEWS
    Computer Software Company18%
    Financial Services Firm12%
    Comms Service Provider7%
    Manufacturing Company7%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Non Tech Company7%
    Hospitality Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company9%
    Comms Service Provider7%
    VISITORS READING REVIEWS
    Computer Software Company27%
    Financial Services Firm14%
    Comms Service Provider8%
    Healthcare Company8%
    Company Size
    VISITORS READING REVIEWS
    Small Business26%
    Midsize Enterprise13%
    Large Enterprise60%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise66%
    VISITORS READING REVIEWS
    Small Business20%
    Midsize Enterprise12%
    Large Enterprise68%
    Buyer's Guide
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: April 2024.
    768,578 professionals have used our research since 2012.