TeamCity vs Travis CI comparison

JetBrains and Travis CI are both solutions in the Build Automation category. JetBrains is ranked #9 with an average rating of 6.8, while Travis CI is ranked #21 with an average rating of 6.0. JetBrains holds a 7.0% mindshare in BA, compared to Travis CI’s 0.9% mindshare. Additionally, 90% of JetBrains users are willing to recommend the solution.

TeamCity

Read 28 TeamCity reviews

2,524 Views
2,249 Comparison Views

90% willing to recommend

Travis CI

Read 2 Travis CI reviews

449 Views
501 Comparison Views

0% willing to recommend

TeamCity

Travis CI

Comparison Buyer's Guide

Download the report

Executive Summary

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

Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation.

To learn more, read our detailed Build Automation Report (Updated: December 2024).

Buyer's Guide

Build Automation

December 2024

Download the complete report

Helped 824,053 peers since 2012

Categories and Ranking

TeamCity

Ranking in Build Automation

9th

Average Rating

8.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Travis CI

Ranking in Build Automation

21st

Average Rating

6.0

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of December 2024, in the Build Automation category, the mindshare of TeamCity is 7.0%, up from 6.9% compared to the previous year. The mindshare of Travis CI is 0.9%, down from 2.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Omakoji Idakwoji

Software Engineer at Home Depot

Build management system used to successfully create full request tests and run security scans

I find the TeamCity backend easily accessible. Users can login to the Linux servers that TeamCity is installed on and perform operations. Also I find the ability to template solutions using the meta runner a good feature as well as the user management feature. There is a display that shows which user made recent changes to a branch on GitHub, including the time the changes were made and the particular agent that ran the job. This is also a very useful feature. The metrics and audit available for projects, pipelines and jobs come in handy when debugging.

Read full review

Pravar Agrawal

Senior SRE at IBM

YAML-based configuration and simple deployment but user interface needs modernizing

Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user-friendly; it feels like it was stuck in 2010. It is very basic and designed for lightweight CI work, and it cannot handle heavy CI. You cannot do branched flows, and you will have to write shell scripts to send calls here and there. The pipelines are not as detailed as some other CI/CD tools. If Travis is down, you don't have any control over it and need to reach out to their customer support.

Read full review

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:

Pros

"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."

"The integration is a valuable feature."

"It's easy to move to a new release because of templates and meta-runners, and agent pooling."

"TeamCity's GUI is nice."

"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."

"Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end."

"TeamCity is a very user-friendly tool."

"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."

More TeamCity pros

"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."

Cons

"REST API support lacks many features in customization of builds, jobs, and settings."

"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."

"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."

"If there was more documentation that was easier to locate, it would be helpful for users."

"The integration between other solutions and TeamCity could be smoother."

"The upgrade process could be smoother. Upgrading major versions can often cause some pain."

"I would like to see an improvement where TeamCity alerts us via email or another medium if there are discrepancies between the code in the staging environment and what has been deployed to production, such as missing updates."

"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."

More TeamCity cons

"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."

Pricing and Cost Advice

"The licensing is on an annual basis."

"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."

Information not available

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

824,053 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

Jan 22, 2015

I generally find TeamCity a lot more intuitive than Jenkins.

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…

Read full review

Top Industries

By visitors reading reviews

Financial Services Firm

27%

Computer Software Company

18%

Manufacturing Company

Real Estate/Law Firm

No data available

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

Questions from the Community

What do you like most about TeamCity?

One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.

See all answers

What is your experience regarding pricing and costs for TeamCity?

Compared to new technologies, TeamCity is more expensive and is an older tool compared to tools like GitLab.

See all answers

What needs improvement with TeamCity?

TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related ...

See all answers

What is your experience regarding pricing and costs for Travis CI?

I'm not too sure about the pricing of Travis or how the agreement works.

See all answers

What needs improvement with Travis CI?

See all answers

What is your primary use case for Travis CI?

Travis CI is mainly used to run integration tests as part of the deployment, which I do on Kubernetes. The Travis workflows are integrated with any changes in my code. It will have different jobs, ...

See all answers

Comparisons

GitLab vs TeamCity

Compared 39% of the time

GitHub Actions vs TeamCity

Compared 17% of the time

CircleCI vs TeamCity

Compared 12% of the time

Harness vs TeamCity

Compared 11% of the time

Tekton vs TeamCity

Compared 8% of the time

More TeamCity Competitors

Tekton vs Travis CI

Compared 76% of the time

GitLab vs Travis CI

Compared 24% of the time

More Travis CI Competitors

Product Reports

Buyer's Guide

TeamCity

November 2024

Download TeamCity product report

Buyer's Guide

Build Automation

December 2024

Download Travis CI product report

Learn More

JetBrains

Video not available

Travis CI

Overview

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

Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia

Facebook, Heroku, Mozilla, Zendesk, twitter, Rails

Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation. Updated: December 2024.

DOWNLOAD NOW

824,053 professionals have used our research since 2012.

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.