SemaphoreCI vs TeamCity vs Travis CI comparison

Cancel
You must select at least 2 products to compare!
SemaphoreCI Logo
261 views|221 comparisons
JetBrains Logo
3,476 views|3,016 comparisons
Travis CI Logo
635 views|776 comparisons
Comparison Buyer's Guide
Executive Summary

We performed a comparison between SemaphoreCI, 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: March 2024).
765,234 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
Information Not Available
  • "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.
    765,234 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
    Ask a question

    Earn 20 points

    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
    23rd
    out of 41 in Build Automation
    Views
    261
    Comparisons
    221
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    6th
    out of 41 in Build Automation
    Views
    3,476
    Comparisons
    3,016
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    17th
    out of 41 in Build Automation
    Views
    635
    Comparisons
    776
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    Comparisons
    CircleCI logo
    Compared 42% of the time.
    Jenkins logo
    Compared 35% of the time.
    GitHub Actions logo
    Compared 24% of the time.
    GitLab logo
    Compared 44% of the time.
    CircleCI logo
    Compared 17% of the time.
    Jenkins logo
    Compared 9% of the time.
    Harness logo
    Compared 7% of the time.
    JFrog Pipeline logo
    Compared 1% of the time.
    Tekton logo
    Compared 57% of the time.
    GitLab logo
    Compared 19% of the time.
    Jenkins logo
    Compared 19% of the time.
    Learn More
    SemaphoreCI
    Video Not Available
    Travis CI
    Video Not Available
    Overview
    With Semaphore, you can easily automate the process of software testing and delivery in the cloud. It is designed to be easy to use and engineered for high performance. It automatically test your app after every change, thus finding bugs before they reach your users. Whenever somebody pushes new code to GitHub or Bitbucket, Semaphore immediately runs all tests, along with any security and style checks that you’ve defined. Once you start using Semaphore, every build automatically becomes a part of the GitHub or Bitbucket pull request review process. It tests multiple projects and branches simultaneously as you push new commits. By default Semaphore automatically builds every new branch in your Git repository. Semaphore’s custom-made platform for Docker equips you with unrestricted access to latest Docker CLI toolchain, including container image caching. Safety net provided by automated CI builds: check. Next up: move even faster with continuous deployment. With a unified workflow for the entire team, Semaphore enables the team to roll-in revisions and gain feedback faster by automatically deploying verified versions of code.

    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
    Dribble, Art Sy, 500px, General Assembly, CrunchBase, Lexmark
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
    Top Industries
    No Data Available
    REVIEWERS
    Financial Services Firm14%
    Computer Software Company14%
    Leisure / Travel Company7%
    Non Tech Company7%
    VISITORS READING REVIEWS
    Financial Services Firm22%
    Computer Software Company14%
    Manufacturing Company10%
    Comms Service Provider7%
    VISITORS READING REVIEWS
    Computer Software Company27%
    Financial Services Firm13%
    Comms Service Provider7%
    Healthcare Company7%
    Company Size
    No Data Available
    REVIEWERS
    Small Business38%
    Midsize Enterprise15%
    Large Enterprise46%
    VISITORS READING REVIEWS
    Small Business24%
    Midsize Enterprise10%
    Large Enterprise66%
    VISITORS READING REVIEWS
    Small Business21%
    Midsize Enterprise12%
    Large Enterprise67%
    Buyer's Guide
    Build Automation
    March 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: March 2024.
    765,234 professionals have used our research since 2012.