# Travis CI Reviews 2026. Verified Reviews, Pros & Cons | Capterra

> Is Travis CI the right Continuous Integration solution for you? Explore 129 verified user reviews from people in industries like yours to make a confident choice.

Source: https://www.capterra.com/p/179183/Travis-CI/reviews

---

Travis CI

4.1 (129)

[View alternatives](https://www.capterra.com/p/179183/Travis-CI/alternatives/)

Provider data verified by our Software Research team, and reviews moderated by our Reviews Verification team. [Learn more](https://www.capterra.com/our-story/)

* * *

Last updated March 13th, 2026

# Reviews of Travis CI

Ease of use

3.9

Customer Service

3.3

## Pros and Cons in Reviews

James P

Senior Software Development EngineerInternet, 5,001 - 10,000 employeesUsed the software for: More than 2 years.

“Travis CI is a continuous integration tool that I find very useful as a Senior Software Development Engineer at \[sensitive content hidden\].“

May 13, 2024

KR

Kitsune R

Lead developerComputer Software, 2 - 10 employeesUsed the software for: More than 2 years.

“Perhaps that was the reason the company started struggling at some point in time - with GitHub and GitLab seriously upping the game, and Circle CI having started quite long ago and moving around faster than Travis CI - it was more inertia and a bit of simplicity that kept me around. And then the company simply ghosted its open source users for something like 4 months, stopping the free service (despite previous promises they wouldn't) and saying nothing on what to expect.“

June 28, 2021

Nelson P

QA EngineerInformation Technology and Services, 1,001 - 5,000 employeesUsed the software for: 1-2 years.

“Travis CI can be easily connected to a GitHub repository, making it easy to automate builds and deployments and guarantee the quality of the code with tests.“

January 19, 2023

RD

Robert D

Sr. EngineerElectrical/Electronic Manufacturing, 10,001+ employeesUsed the software for: More than 2 years.

“Everything, but mostly, debugging build issues and that build environments aren't cached from build to build and have to be completely rebuilt every time and for no reason seem to fail for random issues.“

July 29, 2021

Shubham K

Cloud EngineerInformation Technology and Services, 5,001 - 10,000 employeesUsed the software for: Less than 6 months.

“What I like most is that it takes less time for configuration and It also supports a build matrix feature.“

February 6, 2023

NP

Nicolas P

/Internet, 2 - 10 employeesUsed the software for: More than 2 years.

“Sure enough, you had a banner announcing the change from travis-ci.org to .com , but I didn't understand it would require changes on my side, and I didn't receive an email letting me know that my CI builds would just stop if I didn't manage it.“

June 22, 2021

CR

Chevy R

Solution ArchitectComputer Software, 201 - 500 employeesUsed the software for: More than 2 years.

“A must have for any configuration/development team needing to move fast but also have control over the process to ensure things work as expected.“

May 5, 2022

JC

James C

DevOps EngineerComputer Software, Self-employedUsed the software for: More than 2 years.

“Thanks to bad actors such as unscrupulous bitcoin miners, this once great free open source community service has been morphed into a paid credit-based system. “

September 8, 2021

## Showing most helpful reviews

Showing 1-25 of 129 Reviews

Sort by:

Most Helpful

Rating

Company Size

Reviewer's Role

Length of Use

Frequency of Use

Tamseel A.  
Full stack JavaScript developer  
Computer Software  
Used the software for: 6-12 months

### "Travis CI is great automation tool is easy to configure and run."

October 12, 2019

4.0

We have used Travis ci for automation of code building, testing and deployment. Travis CI is one of the top continuous integration and continuous delivery tool available in the market. We usually use Travis CI for medium scale projects because it easy to use, few minutes of configure is needed comparative to Jenkins which require skilled professional to configure it. We have used it for test projects as it is free for public projects. Travis Ci is good for small to medium scale projects, which doesn’t require much of the customization or less complex projects. Travis CI is also good for public and open source projects because it provides free tier for public projects. It’s easy to use, you don’t need any professional skill to set it up.

Pros

Great thing about Travis CI is it’s easy to use, easy to configure and start running it, you can easily integrate GitHub account and whenever you push your code its integrated and tested on Travis CI. Travis CI doesn’t need hosting server to run it unlike Jenkins which require hosting server. For public projects you don’t have to pay, its free to use for you test and open source projects. Testing on different environment, devices, OS is optimized and run synchronously. You don’t have to maintain software updates for Travis CI unlike Jenkins. It is fast for testing code on different environment by having different jobs like you can have separate job for unit testing and separate jobs for integration testing.

Cons

Travis CI doesn’t have that much flexibility respect to customization as compare to Jenkins. Integration with third-party tools is not too much which reduces it flexibility. You code is accessible to Travis CI which is not good for most sensitive projects. You must pay for private projects as comparative to Jenkins which is free for private projects.

Alternatives considered

[CircleCI](https://www.capterra.com/p/150380/CircleCI/)[Jenkins](https://www.capterra.com/p/171026/Jenkins/)

Reason for choosing Travis CI

Travis require less time to configure and it doesn't require hosting server to host it. Online community support is good too.

Review Source

VR

Verified Reviewer  
Senior Software Development Engineer  
Internet  
Used the software for: 2+ years

### "The code integrates very well"

May 13, 2024

4.0

It has been a very convenient experience, since I can easily see the status of my builds directly from the platform when logging in, it is exactly a good technical process for each build I need, it can be worked very easily in a group.

Pros

Travis CI is a continuous integration tool that I find very useful as a Senior Software Development Engineer at \[sensitive content hidden\]. I love its ability to automate the entire process of building, testing, and deploying software. With Travis CI, I can be sure that any code changes I make will be seamlessly integrated with the main project and tested automatically.

Cons

Integration with GitHub gives me a lot of errors, when logging in, when linking, when unlinking, that is quite tedious and only specialists on my team have found the solution.

Switched from

[Harness](https://www.capterra.com/p/186312/Harness/)

Very complex program in generating easy-to-manage compilations.

Review Source

JS

Jason S.  
CTO  
Computer Software  
Used the software for: 2+ years

### "Pricing Changes, Botched Rollout"

February 1, 2021

3.0

Overall, beyond the pricing switch, I had been very happy with Travis CI. But, after this pricing change without any notice, I have become unhappy with it. At $85/mo to build two projects without any concurrency (it's slow), I'm become less interesting in staying a customer.

Pros

I liked the ease of use getting Travis setup, the caching, and the build matrix.

Cons

I think the concurrency model is terrible. Sometimes when I want to deploy code to staging and production, I have to wait for each PR and commit to build before the push happens. Sometimes this takes 20 minutes for all branches to finish building before a push can happen. Also, I'm very unhappy with the pricing changes roll out. I have been paying for Travis for a couple years now. All of a sudden, my iOS team said they didn't think our builds were working any longer. There were a bunch of builds that didn't go through, saying we didn't have enough credits. Digging in, I realized your pricing model changed. So our builds have not been going through for close to a couple months now. I never received an email that you would be changing the pricing which would then break our builds. This to me is a botched roll out. You should have specifically told me that my iOS builds would stop working. In our dashboard, it just shows that our last build was successful 2 months ago. Not that no more builds were happening. This is unacceptable. So much so, that I am actually now reading the Travis CI to Circle CI migration document. Circle CI seems like a cheaper option for us now.

Alternatives considered

[CircleCI](https://www.capterra.com/p/150380/CircleCI/)

Reason for choosing Travis CI

I believe I will be switch back. Travis seems like the expensive option now.

Switched from

[CircleCI](https://www.capterra.com/p/150380/CircleCI/)

Circle CI seemed to be more friendly to my Ruby on Rails projects. When I switched to a Python project, it seemed like more of the open source python tools that I saw were using Travis CI. So I switched to Travis for this new project.

Review Source

JC

James C.  
DevOps Engineer  
Computer Software  
Used the software for: 2+ years

### "Travis CI: Great overall for over 8 years. Not anymore after travis-ci.COM migration & OSS credits"

September 8, 2021

4.0

Overall, Travis CI used to be the best turnkey solution for independent Open Source developers to set up Continuous Integration and Unit Testing pipelines. Thanks to bad actors such as unscrupulous bitcoin miners, this once great free open source community service has been morphed into a paid credit-based system. Lack of customer support responses have pushed independent volunteer open source developers out. We simply cannot afford CI testing when our software is free and open source by design.

Pros

As a long-time user of TravisCI for 8 years, I loved the ease of setting up CI testing pipelines and testing matrices with a single .travis.yml file. It made testing DevOps Chef cookbooks easy and was a great solution that integrated well with test-kitchen.

Cons

When getting a remote VM testing pipeline set up, there are some barriers to ease of debugging. This was primarily due to the lack of live SSH terminal access to poke around at the testing environment to debug job failures. After they added Debug Mode, this became a bit easier. The main problem with Travis-CI was recently introduced with the travis-ci.COM migration. Users were encouraged to migrate projects over to the new website with no way of going back. A new paid credits system was forcibly implemented, with some promise of Open Source credits. All of my projects on TravisCI were free and OSS licensed, so I asked for OSS credits. After a few back and forth emails, I was promised 25k credits. However, after checking in the OSS credits section I still see zero credits listed. It seems that just like that, Travis CI was taken away from OSS users who chose to migrate with no warning about the implications. Travis CI news blog posts explain that this change was made due to some nefarious bitcoin miners abusing their free build systems to mine cryptocurrency. So just like in school where the bad apple ruins it for the rest of the class, now Travis CI has been taken away from small Open Source developers. Please improve your customer support and reinstate OSS credits for independent Open Source developers! Any kind of response or clarity around the application process would be much appreciated!

Alternatives considered

[CircleCI](https://www.capterra.com/p/150380/CircleCI/)[Jenkins](https://www.capterra.com/p/171026/Jenkins/)

Reason for choosing Travis CI

I used to love the ease of setting up a Travis CI pipeline for Open Source projects. Now there are artificial barriers to doing so.

Review Source

Adam G.  
Director of Information Technology  
Higher Education  
Used the software for: 2+ years

### "Essential for software development"

February 1, 2021

4.0

I am able to conduct a wide variety of tasks from checking compilers, running static analysis, and building documentation.

Pros

Travis-CI was the first CI system I used on my research projects, and to this day Travis-CI still does the heavy lifting on most of my tests during Continuous Integration. It's extremely flexible; I have workflows that run static analysis, security checks, documentation builds, and more. The features and integrations with a number of other systems (GitHub, CodeCov, etc.) make this my go-to CI. I especially appreciate the support for Education customers, other CIs would be quite expensive by comparison.

Cons

Operating systems support can lag. In particular, support for modern C++ compilers can be a bit tricky (it's an old item many of us have raised). The new plans price some organizations (e.g. Boost) out of using it. Support on the MacOS images is not as robust.

Alternatives considered

[GitHub](https://www.capterra.com/p/129067/GitHub/)[CircleCI](https://www.capterra.com/p/150380/CircleCI/)[Microsoft Azure](https://www.capterra.com/p/16365/Azure/)[GitLab](https://www.capterra.com/p/159806/GitLab/)

Reason for choosing Travis CI

Travis-CI provides the best pricing tier for Higher Education. I also use AppVeyor and GitHub Actions, but I've worked with Travis-CI for a number of years, so I have more functionality enabled on Travis-CI than the others.

Review Source

RD

Raphael D.  
Software developer  
Computer Software  
Used the software for: 2+ years

### "Used to be one of the only good option, not so much more today"

February 10, 2021

2.0

We see it here as less and less professional. It started with a lot of time to get new images, the problem of running after 4PM (Berlin time), the cache for ccache that suddenly disappear (which makes us use even more credits, obviously), and we are missing more and more CD. It really feels as if, after Travis was bought, that the board decided to "cash in" money. You even need to pay credits now for OSS? How is that supporting it?

Pros

I liked the ease to setup a new project with it, once you know how to get around the product.

Cons

For sure this new price plan, that was announced a day \*after\* it was put in place (seriously?). It costs us more than half of the credits to make just one build. The price per minute is just insane. I can have more workers and unlimited build times with Azure DevOps, for about the same amount of money of just the subscription alone (so not counting those Travis add-ons). When the credits are done, then the CI will just block. You need to close and reopen the PR. Problem is that we have other GitHub integrations, so this makes the process really painful.

Alternatives considered

[Jenkins](https://www.capterra.com/p/171026/Jenkins/)

Reason for choosing Travis CI

We are actually also using AppVeyor. We didn't choose over Jenkins as it seemed it would still imply too much maintenance time (infrastructure and devop)

Review Source

Francis C.  
Research Software Developer  
Research  
Used the software for: 2+ years

### "review"

February 19, 2021

5.0

It was amazing until the recent price changes.

Pros

Very easy to setup and many integration examples. Multiple services and environments makes it quick to setup for many testing combinations.

Cons

The pricing has gone up drastically recently and without that much time to adapt. The best way to keep services up and running without getting caught back-and-forth requests of build minutes was to move away from the service.

Alternatives considered

[GitHub](https://www.capterra.com/p/129067/GitHub/)[GitLab](https://www.capterra.com/p/159806/GitLab/)[Bitbucket](https://www.capterra.com/p/233341/Bitbucket/)

Reason for choosing Travis CI

Did not choose it \*\*over\*\* others. Each repo has its own use-case and Travis=CI is employed were applicable and still working. If Travis-CI becomes too troublesome or inconvenient, including money/support wise, our team will move toward other solutions.

Review Source

NC

Nicholas C.  
Founder  
Education Management  
Used the software for: 2+ years

### "Easy-to-use product but support for OSS failing"

February 2, 2021

5.0

Pros

I like how easy it is to deploy and get up and running with this software and configuration files, etc (e.g. it's essentially just a commandline which is nice). It was also really nice for all of my open-source projects while travis-ci.org was still running. I could deploy and have builds run without having to worry about money.

Cons

Ever since the move to travis-ci.com, support has been terrible and I've used up all of my free trial credits on my open-source web application's Cypress integration tests (https://github.com/tutorbookapp/tutorbook). I contacted support 5 days ago and still haven't heard back about getting more open-source credits for my account. I seriously miss travis-ci.org (though I completely understand the problems with cryptocurrency mining, etc).

Switched from

[CircleCI](https://www.capterra.com/p/150380/CircleCI/)

I had used TravisCI earlier for building and deployments so I already knew how to use it. I decided to switch back to using TravisCI because CircleCI's configuration just took waaaaay too long to learn and implement correctly.

Review Source

VR

Verified Reviewer  
Developer  
Computer Software  
Used the software for: 2+ years

### "Lots of features, sometimes build issues, a bit slow"

July 1, 2021

3.0

It was a good choice at the time. But I am not sure if there are now better alternatives. I would especially check for a docker based build system.

Pros

Travis has a lot of features which can be setup easily using configuration files. It is free for open source products and not to expensive for company projects.

Cons

Quite often builds are stuck which leads to a huge stop in developments in hour company because we pretty much rely on it. Also the builds starts quite slow.

Review Source

Shubham K.  
Cloud Engineer  
Information Technology and Services  
Used the software for: Less than 6 months

### "Travis CI - My Unstoppable open source integration platform."

February 6, 2023

4.0

my overall experience is moderate.

Pros

What I like most is that it takes less time for configuration and It also supports a build matrix feature.

Cons

What I like least is it provides limited support and have less customization options than Jenkins.

Alternatives considered

[Jenkins](https://www.capterra.com/p/171026/Jenkins/)

Reason for choosing Travis CI

Jenkins CI server provides good customization options.

Switched from

[Jenkins](https://www.capterra.com/p/171026/Jenkins/)

Jenkins CI server provides good customization options.

Review Source

AS

Alex S.  
Data Engineering Lead - SecureX  
Computer & Network Security  
Used the software for: 2+ years

### "Travis CI: One of our sharpest, most reliable, most powerful and transformative tools."

February 24, 2021

5.0

It's a daily productivity driver for our team. Incredibly valuable, reliable, and one of the best tools we have in our development process.

Pros

I pushed hard for my team to build our CI/CD pipeline using Travis. It is just a tremendous tool, and I'm deeply grateful that we have this tool in our toolkit. \[SENSITIVE CONTENT HIDDEN\] said "If I had eight hours to chop down a tree, I’d spend the first six of them sharpening my axe." Travis CI is one of the sharpest tools we have, and it's made a massive difference in speeding up our team's productivity. You guys recently gave us the option to upgrade our private Travis CI to include even higher numbers of parallel builds, which made a massive difference to our ability to grow our development team, and to increase the rate at which we build our own software.

Cons

For a while, we were working very hard on our end to try to figure out how to speed up our builds, and had to do quite a bit of work to try to optimize our software architecture to optimize around the limits on build concurrency in Travis. We made some progress on that, but it was slow going, and ultimately you gave us an option to pay for a higher degree of parallelism.

Review Source

CR

Chevy R.  
Solution Architect  
Computer Software  
Used the software for: 2+ years

### "Review - Travis CI"

May 5, 2022

5.0

A must have for any configuration/development team needing to move fast but also have control over the process to ensure things work as expected.

Pros

Travis CI is a must for our team as we work in an agile environment that requires constantly deployments. Travis makes that easy to do and helps us track/monitor changes and have them tested in real time.

Cons

I have found that the debugging process can be a little tedious because of the lack of information in error messages. I've also noticed some issues where I need to re-run jobs without explanation.

Review Source

VR

Verified Reviewer  
QA Engineer  
Information Technology and Services  
Used the software for: 1-2 years

### "Great tool for CI/CD"

January 19, 2023

5.0

Pros

Travis CI can be easily connected to a GitHub repository, making it easy to automate builds and deployments and guarantee the quality of the code with tests. It also has a big community that helps troubleshoot any issue.

Cons

Travis CI does not offer dedicated build environments for the builds, which means that the builds are impacted by other builds running on the same shared infrastructure.

Review Source

DM

Damien M.  
CTO  
Banking  
Used the software for: 2+ years

### "Works, but deprecated UI"

February 3, 2021

3.0

Pros

It does the job with reliability. I have no reason to change.

Cons

The UI has not evolved for years I think. I'm constantly doing the same 10 clicks to do the same things everyday, that I could have done in 1-click with a better UI. There are no insights, no "nice to have". It may work but I have absolutely no attachment to the product and could change without missing anything. In fact, I'll probably rationalize the number of tools we have by switching to Heroku CI or Github Actions, since they do as much as Travis I have no need for another tool.

Alternatives considered

[GitHub](https://www.capterra.com/p/129067/GitHub/)[CircleCI](https://www.capterra.com/p/150380/CircleCI/)[Heroku](https://www.capterra.com/p/158191/Heroku/)

Reason for choosing Travis CI

Well known. Easy to configure.

Review Source

RD

Robert D.  
Sr. Engineer  
Electrical/Electronic Manufacturing  
Used the software for: 2+ years

### "It's awful, but we are stuck with it"

July 29, 2021

1.0

I hate using it, I never would have recommended it, I want our team off it as soon as possible but the one person that set it up refuses to look at anything else and has the bosses ear. So I'm stuck with this nightmare of a build system that is just AWFUL

Pros

Nothing... I hate this platform. Gitlab is way better for CI/CD

Cons

Everything, but mostly, debugging build issues and that build environments aren't cached from build to build and have to be completely rebuilt every time and for no reason seem to fail for random issues. Like not being able to download a dependency. Or failing to deploy to github releases without an helpful error messages. Or worse, saying you did deploy, but then the package is nowhere to be found, and there is no way to debug this

Reason for choosing Travis CI

I have no idea

Review Source

AA

Aashish A.  
Software Engineer  
Computer Software  
Used the software for: 2+ years

### "Travis CI review"

June 29, 2022

4.0

Pros

This tool is best for mobile app automation. It supports native iOS, Android and other cross-platform like flutter.

Cons

More number of builds are not supporter for a free/indie account.

Review Source

VR

Verified Reviewer  
Site Reliability Architect  
Biotechnology  
Used the software for: 2+ years

### "The long-standing king of open source CI/CD... but will it last?"

July 18, 2019

4.0

Pros

Been using Travis-CI for about 8 years now, and it's always reliably hosted my OSS projects.

Cons

Now with new ownership we've been seeing more downtime. Hope they can keep it afloat!

Review Source

IS

Ibraheem S.  
FE dev  
Sports  
Used the software for: 1-2 years

### "why do i need a title? 🤔"

August 4, 2021

5.0

very happy

Pros

I like that it gives a pride option :D checking previous builds, who issues them and if the failed/passed is very nice. for the most part is is smooth and just does its job.

Cons

finding out why a build failed is sometimes very annoying. scrolling a huge page of logs is not smooth (and maybe some better segmenting options there could be useful) we have a weekly recurring job that fails for linting reasons (but we still need it to run to get sonarQube coverage, idk if this is on us for bad implementation) but then who ever deployed last they get an email saying that the build failed. and we can only opt in or out from the whole thing and not just that type of builds.

Review Source

CW

Chris W.  
n/a  
Computer Software  
Used the software for: 2+ years

### "Fast, free (for OSS) continuous integration testing"

March 13, 2021

4.0

Ensuring that the master branch of my projects remains stable and of release quality, by only allowing changes that pass CI to be merged.

Pros

Web interface is fast and responsive. Builds are quite fast. It's free for OSS. Quite good documentation (comprehensive). Supports several environments, including Macs (and now Windows too).

Cons

Not so easy to determine exactly what you need to run (e.g. which packages to install, what to sudo). A simulator/interactive environment for testing would be nice!

Reason for choosing Travis CI

We are also using Appveyor for Windows builds, because Travis did not support it at the time. However its web interface is much slower, its builds are slow, and documentation is not as good. Circle CI was frustrating to set up, and didn't seem to offer any advantages.

Review Source

AC

Aldo C.  
IT devops  
Education Management  
Used the software for: 1-2 years

### "Review for Travis"

October 19, 2022

5.0

Pros

I like the ease to setup the CI for automating the deployments in the different applications

Cons

probably the cost if you can start to use it and don't have an idea of estimate cost

Alternatives considered

[Jenkins](https://www.capterra.com/p/171026/Jenkins/)

Reason for choosing Travis CI

for use the open source applications

Review Source

SL

Stephen L.  
Senior Lecturer  
Computer Software  
Used the software for: 2+ years

### "Great for Budding Software Engineers"

June 9, 2021

5.0

Using Travis CI (educational plan) has helped my students to gain some real-world devops experience. It has allowed me, as an educator, to offer them this experience.

Pros

I use Travis CI in my software engineering class so that my students can build and deploy to cloud-hosted websites. My students find it relatively easy to setup and use. As an educator I have oversight over all of my students' projects. I find the build history particularly useful as I can see how often builds are occurring and whether they are passing or failing. Ideally, projects should be built often and most builds should succeed. Travis CI really helps me to assess these aspects.

Cons

There are no real cons that I can think of.

Review Source

PL

Praneet L.  
developer  
Information Technology and Services  
Used the software for: 2+ years

### "Falling behind"

March 20, 2021

3.0

Pros

Everything listed in the Cons section? :)

Cons

Lack of first-class support for build artifacts. The configuration format for a multi-stage pipeline isn't straightforward and a bit unusual among the competition. No support for 3rd-party extensions.

Review Source

VR

Verified Reviewer  
Tech Lead  
Internet  
Used the software for: 6-12 months

### "Great option for testing - particularly for open source"

March 29, 2019

5.0

Pros

I have used Travis CI for open source software development for quite a while, and always found it to be reliable and easy to set up. The container-based approach makes the testing quick and repeatable, and the UI makes it very to see where your issues are. It also has brilliant integration with github, so that pull requests and branches can be tested independently, and results are shown right in the github UI.

Cons

I've wanted to trial this in a commercial environment, and was disappointed by the lack of a free private tier to get started.

Review Source

CJ

Carlo J.  
Senior Frontend Developer  
Computer Software  
Used the software for: 2+ years

### "Open Source Software"

February 14, 2021

5.0

Pros

I used to like your approach to give back to the open source community.

Cons

That you changed your approach to giving back to the open source community.

Reason for choosing Travis CI

I'm actually reconsidering to continue using travis.

Review Source

EV

Erik V.  
Senior Database Programmer Clinical Trials  
Research  
Used the software for: 2+ years

### "Switching to gh-actions"

February 8, 2021

5.0

Very pleased with the product

Pros

Works and integrates seemlessly. Love it.

Cons

Pricing model has changed. I understand. We are open source and non-profit so moving away.

Review Source

Similar Products

Featured