# Page 2 | Travis CI Reviews 2026. Verified Reviews, Pros & Cons | Capterra > Page 2 - 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 # Page 2 - Reviews of Travis CI ## Showing most helpful reviews Showing 26-50 of 129 Reviews Sort by: Most Helpful Rating Company Size Reviewer's Role Length of Use Frequency of Use MW Matthew W. Project Lead Internet Used the software for: 2+ years ### "Static matrices and changes to OSS terms mean I cannot recommend the product" June 28, 2021 3.0 Our initial years with Travis were successful, and we were quite happy with the product. But over time, the lack of flexibility meant struggling to create and deploy our CI definitions. But the part that killed Travis for us was the change to OSS terms late in 2020. We'd already noticed that our queues would become long, particularly if we had many contributors or maintainers working simultaneously. But with the changes in terms, we quickly ran into a scenario where we ran out of hours by mid-month. This left us with an untenable situation; as an OSS project, we have limited funds, and we would quickly run through those if we purchased a plan. As a result, we are within 1-2 weeks of moving off the platform entirely. Pros When we first started using the product, it was one of the few that existed, and it provided us exactly the assurances we needed to have predictable, stable software releases. Idempotent runs made it possible to know exactly when and why something failed. Cons Since we produce OSS libraries, it's important for us to test against each language version we support. Unfortunately, there is no way in Travis to dynamically create a matrix based on the library/package definition itself. For instance, we produce PHP libraries, and our package management solution, Composer, allows us to specify in the package the versions we support. Unfortunately, when we change those, we also need to remember to change the Travis definitions to reflect those changes. This becomes a source of error very quickly - Travis may report all is green, but it turns out we haven't added the new PHP version to the matrix, so it's a false sense of assurance. On top of that, it's impossible to succinctly make discrete jobs that do different things. For instance, I don't need to run coding standards checks, static analysis, and documentation linting for every single job in the matrix; I really only need to run these once. But to do that, Travis forces me to define env variables for jobs, and then use conditionals to determine what to run. This makes the CI definitions very convoluted, and, if you have a lot of repositories that need to do the same, hard to distribute when you have changes to make. Other CI systems address this. Review Source Ian M. Head of Product Internet Used the software for: 2+ years ### "CI tool that has a lot of value for the money" February 27, 2020 5.0 I started using Travis initially because I needed a way to have consistent builds of our desktop software (built on Electron). Travis has just the tools I needed to make this happen. Doing local builds of the software was processor intensive, I had to go check the status of the build and I was always changing software on my local machine so sometimes builds would fail because I changed something. Travis has completely containerized build machines so you get the same result every time. We now use it for building all our software. I don't know what we'd do without it. Pros \* Affordable (it's priced based on users/seats) \* Documentation is solid and easy to follow. I've never needed to contact support. There's good online Q&A since Travis has a large user base. \* Versatile (whatever software you're building, there's a recipe for it) \* Github integration : you get realtime build status RIGHT in Github which is awesome, once you get your system set up, you rarely ever visit Travis again. It just works. Cons There's really nothing I didn't like about Travis. Some of the quirks of Electron were the trickiest things to figure out, but that's not Travis's fault. There's a little learning curve when you go from building locally to building remotely with Travis where you need to understand how to set environment variables and retrieve those values in your config/script. Reason for choosing Travis CI We didn't look at other options. Circle CI would have been the likely comparison but I don't think at the time we made the selection there was much online about Circle CI supporting Electron builds. It may have been possible, but the Electron community was definitely more affiliated with Travis CI. We knew we wanted something hosted, so we didn't look at Jenkins (which, I think, requires you to host and manage it yourself). Review Source NP Nicolas P. / Internet Used the software for: 2+ years ### "Loved Travis in the past, sad to be on my way out." June 22, 2021 3.0 Between the cons described above, the service degradation I've observed in the past 6 months and your recent organizational and pricing changes (we are an open-source project and directly impacted), I'll be setting up Github actions to run my CI tests from here onwards (this is also about standardizing with other projects in my organization) and will deactivate my travis account. Pros It worked really nicely until about 6 months ago ! The previous unlimited open-source plan was generous, and a huge selling point. Cons Service has been less than ideal since the decision to move OSS projects travis-ci.org. We have felt this throttling of resources, and it was an indication that things were about tho change for the worse. I was surprised to find that from one day to the next my CI builds weren't being run anymore. 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. I'll admit my fault in not checking more thoroughly. Moving from .org to .com was not as easy as I would have liked (Why do I need to sign up for a beta? Why is it in beta, and why do you need more decisions from me that I don't have all the information to decide?), but I eventually got there. Review Source Elliott L. Developer Computer Software Used the software for: 2+ years ### "Really simple to use continuous integration." July 18, 2019 5.0 Pros We use it to run php unit tests whenever we commit code to a repository. All we have to do is include a file in the root of the project and enable the project in the travis interface. Takes less than 5 minutes to set up fully automated unit testing. Much more easy than setting up your own CI pipeline with the huge amount of different apps that exists. Generous free tier. Cons Can be slow at times, documentation can on occasion be more minimal than I would like. As a developer you get used to this though, there are always loads of examples online. Alternatives considered [GitLab](https://www.capterra.com/p/159806/GitLab/) Reason for choosing Travis CI Travis works on all major providers. Review Source Ondřej P. Software Architect Computer Software Used the software for: 2+ years ### "Past Glory" February 1, 2021 1.0 We started using Travis in September 2016. Over the years we used it for both CI and CD pipelines for most of our applications - we had about 300 pipelines. For many years it was a truly great service. Now days we're trying to move away as fast as we can. Pros Worked like charm years ago and did everything we ever wanted to. Neat debugging feature. Cons In past 2 years Travis is dying in painful agony. The service is unreliable, sometimes not working for days. Status page is not updated at all. Support is non-existent - time to first response to an issue is a month now. Out of about 20 issues we raised in past year, not a single one was resolved. Reason for choosing Travis CI It was much easier to use then Jenkins and was a great service in the past. Review Source Bruce B. Senior Operations Officer Research Used the software for: 2+ years ### "Powerful, free and easy DevOps" February 3, 2019 5.0 Travis hasn't let me down yet. This services handles more than 90% of our builds. Pros Travis does a few things really well: 1. Documentation - the documentation is extensive and complete, and one never has the feeling that there are "hidden features" that only the power users know about. 2. Speed - waiting for more than a few seconds for a build to start is extremely rare. 3. Deploy integrations - builds can be deployed to a set of services easily. This is probably the easiest way to set up continuous deployment if you're on a tight budget. Cons The build environment can be somewhat restrictive, forcing one to choose language-specific base images and not giving access to the underlying VM. Review Source DY Denis Y. Co-Founder Design Used the software for: 2+ years ### "Good product, but very expensive" April 1, 2021 5.0 We are using Travis CI mostly for our products that have a PHP backend and a Angular PWA application. We are prerendering all pages in our CI process which, for some reason got really slow in the last 12-24 month. I dont know if Travis CI is limiting external HTTP requests (which we rely on to get the content to render). For example a project with 500 subpages takes 30minutes to render. We already checked our Backend endpoints and these are not the limiting factor. Running is locally is has a built time for around 5-6 minutes. Pros I like the ease of deployments especially with multi-step-deploys of websites where the backend and frontend should be in sync. Cons Only thing I need to complain is the pricing. For a small design and development agency like us the price of the "concurrent job"-based plan is way too expensive while our current credit-based plan (which i'm happy that this exist) is very often exceeded due to the nature of our deployments. Reason for choosing Travis CI We are using both currently. Travis CI has advantages in the control of the jobs while our latests test showed us that GitHub Actions is running way faster with our setup (described above) Review Source EB Eric B. Software developer Research Used the software for: 2+ years ### "Hard to beat such an offer when in academia" July 6, 2021 5.0 The reproducibility trend is gaining momentum within the academical research community. CI usage, now a must have for software engineering concerns, can easily be stretched to address reproducibility issues and is thus being rapidly adopted. Pros \- navigating the smooth and complete interface (with a nice github integration) - logs are detailed, thorough and hosted for a long time - jobs don't get to wait for long delays once triggered - great (and generous) customer support - nothing to install on premises Cons Every CI offer must face quite technical challenges to address specific/advanced services like dealing with credentials or managing sophisticated job workflows. Travis CI does the job quite nicely on such issues yet the learning curve can be quite steep at first. Yes, Travis CI does offer a thorough documentation, yet getting all the tidbits properly aligned can be a tedious task at first (your mileage may vary). Reason for choosing Travis CI Travis CI is really mature (complete APIs), highly customizable in its usage, reliable and seamlessly hooked-up with github hosted repositories. Review Source Charlie M. Engineering Lead Industrial Automation Used the software for: 2+ years ### "Fair, but unclear" August 25, 2021 5.0 Good, but can be Pros Travis is the only ci tool that have VT-x enabled! It's also well known, simple to use. Cons Paid compared to github action. At least it could be cool to have come montlhy free credits, for just a few to maintain some OSS project in RUN mode. Not so configurable: I can't come with my own VM ISO so I'm forced to download all prerequisite package every time for each builds: most of my credits go there... As I'm part of multiple orgs, it's hard to know which credits are spent where. Also, the authorization mecanism is not that clear: I don't know exactly what travis sees from my github infos. Reason for choosing Travis CI No VT-x on the others: I use the others for my non VT-x test suites, so travis is not my first choice when looking at CI for OSS (and even company project where we have our own autoscaled gitlab runners. Review Source JW Julian W. Lead Developer Renewables & Environment Used the software for: 2+ years ### "Good CI" February 28, 2021 4.0 Travis builds, tests and deploys our software to staging and production environments. It is immensely useful, and critical to our software development pipeline. Pros Generally very reliable, customizable, extensible. Easy to debug. Is a workhorse. Cons Sometimes you'll get builds that won't debug, or builds stuck in the queue forever. This is generally because of some piece of travis infrastructure that has suddenly stopped, but there are no notifications, nor status indications that anything is wrong. Customer service can take the better part of a week to respond, or not at all. Alternatives considered [CircleCI](https://www.capterra.com/p/150380/CircleCI/) Switched from [Jenkins](https://www.capterra.com/p/171026/Jenkins/) Simpler, cloud hosted. Review Source Dimitrios-Iason K. Support Escalation and Test Lead Computer Software Used the software for: 2+ years ### "All good -- minor suggestions for improvement." July 7, 2021 4.0 Pros The product is easy to use -- even non-technical people in our team are able to have a look at it and understand why a test failed. It is good that it provides much info about each step it runs Cons The dev documentation can be improved -- we had some hard time setting up our acceptance test infrastructure as it wasn't clear to us where to set environment variables. Sometimes it takes a long time for Travis to indicate that a GitHub PR is being tested by displaying the orange dot -- not sure if this is a Travis or Github issue, though. Review Source VR Verified Reviewer Web Developer Computer Software Used the software for: 2+ years ### "Nice GitHub Integration" July 2, 2021 4.0 Pros I like that I can see the live status from GitHub and that the UI is very simple. I can easily find everything. The console output is colorized (it's not in other CI software I've used). Cons Sometimes parts of log output is collapsed, which has hidden an error for me before. It took a while, but my team figured it out. Review Source MSD M. Serhat D. Senior Software Engineer E-Learning Used the software for: 2+ years ### "One of the pioneers of CI/CD" April 2, 2020 3.0 I would say 'yes' for TravisCI 2 years ago, but nowadays there are better alternatives to this product, such as Github Actions. My overall experience with TravisCI started quite positive but ended negatively because of the unreliable service they are providing at the moment. If you are running a critical business with 0 tolerance to downtime, TravisCI wouldn't be a wise choice nowadays. Pros TravisCI did a great job for many years, across different CI/CD tools, by providing a rich feature set and well-documented functionality. Cons Unfortunately, TravisCI is not very reliable. It's having constant downtimes for many months. TravisCI announced the deployment API v2 for a long time ago, but never released the stable version. On the other hand, after the recent acquisition of Idera, many talented developers have left the company. Therefore their development speed and shipment of the important features seem to be delayed. Review Source ES EMANUELE S. Software Development Manager Information Technology and Services Used the software for: 1-2 years ### "CI / CD in a simple way" February 2, 2021 5.0 I'm very happy about Travis, until now I found always an answer for each need I had Pros 1\. Documentation, maybe the most important value 2. Configuration flexibility in particular GIT SSH custom keys, env variables with sensitive information, build trigger (with inline configuration... very useful for testing configurations), machine SSH encrypted keys, configuration imports, custom scripts 3. Easy integration with GitHub Cons Permissions check (it's not so clear understand who can build, who can view build history, who can edit configuration). Alternatives considered [CircleCI](https://www.capterra.com/p/150380/CircleCI/)[Ionic](https://www.capterra.com/p/206394/Ionic-Framework/)[TeamCity](https://www.capterra.com/p/136011/Teamcity/) Reason for choosing Travis CI I already knew TeamCity but there wasn't a cloud version when I choosed Travis. Ionic has a ready to use mobile app configuration and we use it. I never had enough time to setup a Travis configuration build successfully a ionic app. Review Source MG Michael G. Postdoctoral Researcher Research Used the software for: 2+ years ### "Broken promises" March 18, 2021 1.0 Horrible. Broken promises. Unresponsive support. Will not use it, and I will aggressively move anyone I collaborate with off Travis as quickly as possible. Travis breaking the open-source infrastructure has already cost me days if not weeks of additional work. Pros Before Travis got bought out and reneged on their promise to support open-source software, it was a cornerstone of my open source work. Alas, in its current form, I wouldn't touch Travis CI with a 10-foot pole. The only reason I still interact with it at all is that one of those projects is specifically for deploying documentation via Travis. As soon as I can move the project in a new direction, I'll be done with Travis for good. Cons Travis broke their promise of supporting Open Source with free CI service. I requested OSS credits months ago and got no reply. It's not that the paid tiers are prohibitively expensive. In principle, I might be able to expense CI costs. However, Travis' actions have eroded any and all trust I might have had in them, so I would not do business with them at any level Reason for choosing Travis CI I did not choose Travis CI. I am actively moving from Travis CI to Github Actions for all my open source work Review Source Ramindu D. Software Technical Lead Computer Software Used the software for: 2+ years ### "Effective continuous integration on the cloud" January 9, 2020 5.0 Travis CI helped my teams build continuous integration pipelines running on Github projects extremely easy and rapid. Pros Travis CI is the go-to continuous integration tool for open source projects thanks to its tight integration with Github. It provides a great set of tools on the cloud for integrating existing and new Github projects, configuring their build parameters and running builds based on various Github events such as the opening of pull requests which gives an unprecedented level of control to project leads on how code is merged in to projects. Cons Travis is a bit complex to integrate with version control platforms other than Github. Configuration to make it work with other platforms such as private GitLab servers can be tricky. Review Source TJ Tim J. Senior Principal Software Engineer Information Technology and Services Used the software for: 2+ years ### "Customer service is terrible" May 12, 2021 3.0 Fine until I tried to talk with support. Pros It does the job it is intended to do. For years I haven't had complaints until I had to deal with customer service... Cons Customer service is terrible. Turn arounds are 24 hours are more. Responses are unhelpful and sometimes there's no response at all. My most recent experience involved trying to get a new hire access to our projects/org in Travis. He sent multiple emails back and forth with support, each time they said they'd fixed it and nothing had changed. Eventually he stopped getting responses. I also tried submitting a ticket and got no response at all. Reason for choosing Travis CI Don't know but my team is now starting to transition to Drone because the support is so terrible. Review Source KR Kitsune R. Lead developer Computer Software Used the software for: 2+ years ### "Lackluster in features and updates recently, dumping the open source community last year" June 28, 2021 2.0 It was pretty much ok, even though the CI infra stayed behind the competition in terms of software used in builder images, and also available features. 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. Needless to say, for CI it was a complete dealbreaker. I went away and never looked back. Pros Back when I started, the onboarding was very straightforward, as long as you used GitHub. Fairly reliable for my low-profile usage. Simple and direct user interface. Cons It grew worse when the company behind Travis CI got sold; downtimes became more frequent, builder image upgrades didn't really get up to speed - but the worst was to leave an extremely short runway to the free tier for open source users with no prior announcement. That's not so much about the software, it's about the company. Free tier or not, in CI segment you just can't afford such things. Review Source Samwel O. Backend Developer and Site Reliability Engineer Computer Software Used the software for: 2+ years ### "Travis CI Review" May 30, 2019 5.0 I have only used Travis CI on Github repositories so I am not sure how it works with other code hosting providers. In Github, It works like a charm. Pros Travis CI is easy to use, it has a nice and easy user interface that gets you started quickly. Travis CI is well documented which makes onboarding easy. Some of my associates thought that when you have private repositories, you have to pay to use it. I have been using it with my private repositories. If before you had to pay, now things have changed. It would be nice to help support the product though so that development can go on. The servers also require funds to run. Cons Everything is perfect as per now. I have not come across any issues. Review Source TM Timothy M. Software Development Team Lead Information Services Used the software for: 2+ years ### "why is a title required?" July 6, 2021 3.0 Pros Its easy to use by default in new Ember web apps. Cons All configuration goes in a single monolithic travis.yml file, and the syntax of this file is very mysterious. Understanding what a particular configuration does is difficult, and its difficult to figure out how to satisfy new requirements. In contrast, github actions allow for the separate configuration of many different workflows, and offer comparatively much better documentation. We mostly continue to use travis because we've already figured out how to configure it for our basic needs with a few projects, and our company has already purchased a plan. Its difficult to switch to another system, largely due to company politics. Review Source VR Verified Reviewer Director of Marketing Hospitality Used the software for: 2+ years ### "Travis CI is the Godfather of CI" January 15, 2019 4.0 Pros For some reason Travis CI seems like the Godfather of CI even though it popped up at the same time as the others. I think this is because they aggressively had a bot add testing to open source projects, and it seemed to work. Cons For the price even though Travis CI is great its a little expensive. Review Source SG Stéphane G. Software architect Telecommunications Used the software for: 2+ years ### "New travis and chrome webdriver (java8 and java11)" February 4, 2021 3.0 I use travis for continouse integration and continous delivery of NoraUi Open source Framework Pros multi compilation Oracle Java8, OpenJDK8, Oracle Java11, OpenJDK11, nodeJS, ... Cons In new or last version of Travis-CI, I have often this error with the Chrome webdriver: "web view not found" My builds use 4 instances (Oracle Java8, OpenJDK8, Oracle Java11, OpenJDK11) and I still have several instances that do not go through because of this error; it is never the same who do not pass. by relaunching several times it can work. Reason for choosing Travis CI I wanted the continuous integration and continous delivery to be public because the project is Open Source on github Review Source Richard Q. Senior Software Developer Internet Used the software for: 2+ years ### "Travis-ing" November 11, 2021 4.0 Pros It works. Which is always a good thing. Other tools exist, but Travis always seemed the simplest to implement with GitHub. Cons Seemingly no reason to change things but reworking the domain. Not exactly sure what the whole point was. Switched from [Travis CI](https://www.capterra.com/p/179183/Travis-CI/) Compulsory due to domain name change. Review Source GR Griffith R. Postdoc Research Used the software for: 2+ years ### "Largely self-taught, test driven developer" March 12, 2021 4.0 It's the core, it's the standard, and it does work fairly well. I'm kind of surprised it isn't as straightforwardly automatic to sort from GitHub, and there are some confusing elements to enabling it (and I don't quite understand why it's not more integrated with GitHub actions but maybe I'm wrong on that) but it's the standard, and automating test suits is crucial to good, maintainable code (especially if maintained by a community). Pros It's free if your code is open source and lots of other services (like zenodo, netlify etc.) already sort out interoperability, usually a bit sooner than gitlab. Cons It might be a lot quicker/better maintained for non-free use, but the options for testing packages in R, for example, are kind of weak and very slow (assuming the examples I've come across are standard). The fact that they only include python2 by default, plus some permission issues means packages using reticulate (for python/R interoperability) have a bit of a pain to get going (and it takes a long time to test). I guess if default options could be better maintained that would be much appreciated. Alternatives considered [GitLab](https://www.capterra.com/p/159806/GitLab/) Reason for choosing Travis CI I didn't choose it, my employer did and to work with colleagues this was the only real option. Review Source PG Pablo G. Software developer Financial Services Used the software for: 6-12 months ### "Functional, but can be better" April 27, 2021 5.0 Honestly I can't say it is better than jenkins. I assume for the compay not having to deal with management and updates is an advantage, but from a user point of view is more or less the same thing. And jenkins blueocean looks way better. Pros It works. Does what I expected. Not a fan. Cons UI has lots of room for improvemente. As an example Logs screens are annoying, because the scroll hides the header. I only want to scroll the log , not the full screen. When I hover over a build I see a message like 'build #123 passed'. The build number does not tell me anything, it would way better to see the author and the message of the commit, it will save me a click Everywhere you have a commit you should see a tooltip with author/message, not just the link to github Switched from [Jenkins](https://www.capterra.com/p/171026/Jenkins/) job change Review Source Similar Products Featured