--- title: Travis CI Reviews meta_title: 'Travis CI Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 92 reviews by the users' company size, role or industry to find out how Travis CI works for a business like yours. aggregate_rating: rating_value: 4.5 review_count: 92 scale: '5' date_modified: '2026-07-12' parent_category: name: CI/CD Tools url: https://www.g2.com/categories/ci-cd-tools --- # Travis CI Reviews **Vendor:** Travis CI **Category:** [Continuous Integration Tools](https://www.g2.com/categories/continuous-integration) **Average Rating:** 4.5/5.0 **Total Reviews:** 92 ## About Travis CI Founded in Berlin, Germany, in 2011, Travis CI grew quickly and became a trusted name in CI/CD, gaining popularity among software developers and engineers starting their careers. Today, developers at 300,000 organizations use Travis CI. We often hear about the pangs of nostalgia these folks feel when they use Travis CI, as it was one of the first tools they used at the beginning of their career journey. To learn more or for a free trial, visit www.travis-ci.com ## Travis CI Reviews ### 1. Fantastic Continuous Integration System **Rating:** 4.5/5.0 stars **Reviewed by:** Kevin Patrick W. | Software Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** January 30, 2016 **What do you like best about Travis CI?** I write some new code. I push that new code to my repo. Now it is getting built and all the tests are running on Travis CI. If they pass and everything works, that code gets deployed into production - simple and automated. Takes a little bit of configuration and setup initially but payoffs greatly in the end. **What do you dislike about Travis CI?** I have no complaints right now. So far it has been very straight forward and easy to use. **Recommendations to others considering Travis CI:** Right now, for independent development this system has worked great. I can't speak to larger projects or enterprise projects but I think it is worth considering if you are an independent developer or a smaller group of developers. **What problems is Travis CI solving and how is that benefiting you?** I usually write code online in a cloud editor. I then push my code to Github. This triggers a build of this new code in Travis CI. If this code passes the build and test process then it triggers a deployment in Heroku. ### 2. Free CI for my github projects! **Rating:** 4.0/5.0 stars **Reviewed by:** Cho Yin Y. | System Administrator, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** January 29, 2016 **What do you like best about Travis CI?** The seamless integration with Github is the feature I like the most. Travis CI provides free continuous building with open source projects hosted on Github. Unlike other CIs, running Travis is as simple as adding a configuration file to your existing repositories on Github. The configuration file can be easily made with reference to their extensive documentation. Also, Travis allows root access which is a nice feature as well. **What do you dislike about Travis CI?** The builds sometimes compile very slowly. Also, since it is run on Ubuntu and its dependencies aren't always up to date, which implies one needs to add more to the configuration files, slowing the process. However, I do not think it is a big problem for me. Also, Travis runs on Ubuntu and not on Windows, which means cross-platform compilation is made harder. **Recommendations to others considering Travis CI:** If you use Github, then Travis CI is a no brainer. Try it out! **What problems is Travis CI solving and how is that benefiting you?** Continuous integration for private repositories hosted in Github. Travis CI private builds are free for students through the Github Developer Pack. ### 3. The most easy to run CI **Rating:** 5.0/5.0 stars **Reviewed by:** Jonatan Ezequiel S. | Android Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Travis CI?** The best I like it's the way that match with github projects. In my case, I'm using Travis CI to build my open source projects and projects where I work as a collaborator. **What do you dislike about Travis CI?** What I dislike it's how to configure. Sometimes the travis.yml file don't work as expected or some commands are not running. And you have to dedicate a little bit of time thinking on how to structure the travis.yml file. **Recommendations to others considering Travis CI:** Depending on the project you want to run with travis CI take care about how to config the travis.yml file from your git repo. **What problems is Travis CI solving and how is that benefiting you?** In this case, are open source projects. It's a fast to start CI. I like the simplicity. ### 4. Automation is a must have in your toolbelt **Rating:** 5.0/5.0 stars **Reviewed by:** Filipe O. | Senior Software Architect, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** January 27, 2016 **What do you like best about Travis CI?** Travis is very easy to setup for any of your projects, and it's free to public projects on GitHub. The UI is great and it gives hints to help you finding out what you've configured wrong. Giving that build automation is a must have in your toolbelt nowadays, Travis is of course the best choice for public GitHub projects. **What do you dislike about Travis CI?** The paid plans are very pricey, which avoids me to use this great tool in my startup projects at MVP stages - in which I have no profits yet. I think there could be a cheaper plan, even if more limited, for startups at MVP, because build automation is a must. **Recommendations to others considering Travis CI:** You can take a lot of advantage of using Travis for your open source projects. If you don't write tests yet, learn it now and integrate your projects with Travis. Let some tests fail and you'll understand how Travis automated build and emails are a lot helpful. The paid plans are pricey but worth the job. **What problems is Travis CI solving and how is that benefiting you?** I've been convinced to open source many of my private libraries only to get advantage of using Travis for free. Automated tests are very helpful on discovering issues early, and a build automation tool which emails you in case of any failure will be your best development friend. I can't think on starting a new project without Travis. ### 5. The amazing Travis the Tester **Rating:** 4.5/5.0 stars **Reviewed by:** Gabriel F. | Summer Intern, Financial Services, Small-Business (50 or fewer emp.) **Reviewed Date:** March 30, 2016 **What do you like best about Travis CI?** Travis keeps check on all my builds, running the tests it's configured to run. Travis CI not only runs tests on your master developing branch, it may also be configured to test all your feature branches and even Pull Requests, which an amazing feature as it tests a pull request before you merge, simplifying the process and saving you the time. Travis also works as a guarantee for users of your software, as they can see the test log online. **What do you dislike about Travis CI?** I think that Travis is a bit difficult for new users and developers, especially configuring it for the first time. **Recommendations to others considering Travis CI:** Study Travis CI documentation before trying to integrate it, otherwise you'll waste lots of time with mistakes. **What problems is Travis CI solving and how is that benefiting you?** I use Travis CI everytime I'm developing open-source software as it not only checks my code as it shows I value a test-driven environment. ### 6. A great public continuous integration service **Rating:** 4.0/5.0 stars **Reviewed by:** Micah H. | Site Reliability Engineer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** January 23, 2016 **What do you like best about Travis CI?** Travis CI is a great CI service for just about any Open Source (linux-based) project. Things they do well: • Dead simple setup and integration. • Easy integration with Github • Great documentation, I've never needed to file a support ticket. It has been a few years since I've looked into their private repository pricing, but their public service is top notch. **What do you dislike about Travis CI?** The wait times can sometimes get pretty long, but if you're not paying for the service, that is generally more an annoyance than a blocker. **Recommendations to others considering Travis CI:** Travis CI is probably what you'll want to use for most Linux based Open Source projects. If you have other OS requirements, you'll probably need to look elsewhere. **What problems is Travis CI solving and how is that benefiting you?** We needed a simple solution for running tests on Open Source projects, and TravisCI is easy for contributors to integrate with, and reliable as a provider. ### 7. Probably the best CI platform for open source **Rating:** 4.5/5.0 stars **Reviewed by:** 佳亮 . | Mid-Market (51-1000 emp.) **Reviewed Date:** May 27, 2016 **What do you like best about Travis CI?** The integration with other platforms like Github and Bitbucket is just fascinating. Once configured, all you need is a simple push to start a new build cycle. Besides, if the build failed, it will email you, which I feel is very considerate and helpful. **What do you dislike about Travis CI?** The YAML config file is not very friendly to novices. Also, the build environment is not completely the same as local environment. As for iOS development, I've had experience when the build is OK on my computer but failed on CI environment. **What problems is Travis CI solving and how is that benefiting you?** I'm using Travis CI to build and test my open source projects. It really helps improving the quality of every push, every pull request and every merge. ### 8. The CI server you'll love to use with Github **Rating:** 4.0/5.0 stars **Reviewed by:** Abhas B. | Trainee Decision Scientist, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Travis CI?** I like most the Github integration part of Travis CI. When you have an existing Github (either open source or closed source) project, it can work seamlessly with the existing structure and integrates on 1-click without almost any effort on your part. The only thing that you need to add is a configuration file, which is usually very well documented in their docs and also shows the whole log of what happens during the build, so you can catch your mistakes easily. **What do you dislike about Travis CI?** Travis CI is essentially a linux only CI. They say they are working on supporting Mac as a platform too, but due to the nature of licensed products, I dont think it will be free to use for open source projects like the existing one. It doesnt seem like a huge put-off considering that it is the best and easiest CI server I have used, but if you are working on a cross-platform tool, it is downright essential that your tests work on all platforms in the same manner so that you can save your devs the headache of maintaining and testing on different OS. That is where it falls short, it doesnt support Windows or doesnt plan to in the near future. You might not care about programming on Windows, but you do need to care about your users on that platform and make sure that they get the same great experience as others. That is why testing on all platforms are necessary, but sadly using only Travis CI you cant do that. You need to also use something like Appveyor to test on Windows. **Recommendations to others considering Travis CI:** Travis CI is not a cross-platform solution, you'll also need some other CI that builds on Windows for cross-platform projects. Appveyor can fit the bill there. **What problems is Travis CI solving and how is that benefiting you?** I am using Travis CI to test my python modules on linux, including some open source projects. Earlier, it used to be that devs tested all the code on their own machines locally before pushing to Github and make sure all the tests passed. But the problem is, this test results are only available to that particular dev and so others working with him cant be sure of the code quality, specially when the submitter is new-ish. Its much better when everyone can see how that Pull Request performs with existing test cases and be sure that nothing much will be broken if it is merged. Also, when a issue/bug is reported, it is sometimes hard to replicate for others and the question comes of whether it is because of the configuration of that particular machine, or a weird bug in the project itself. So, putting that potential bug as a test case lets us see the status on the CI and determine if it exists on a standard system. ### 9. Travis CI is an excellent test automation tool that integrates seamlessly with Github **Rating:** 5.0/5.0 stars **Reviewed by:** Todd B. | Chief Product Officer, Founder, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Travis CI?** Travis CI is a real life-saver if you need to test your application against different environments. You can test against different language runtimes, different web browsers, different web servers, you name it. The best part of this is you can mix and match these any which way using test matrices. This is just something you can't do manually. Travis CI includes most commonly used computer languages and server technologies. However, if Travis doesn't have something that you need built-in you can script its installation yourself. As long as something can be scripted you can use it on Travis. And really, what can't be scripted? The integration with Github is really great. Most of our staff live in Github and don't even need to go onto Travis CI's website. Every pull request and commit shows the current build status right within Github. **What do you dislike about Travis CI?** When trying to get a build going specifically for the Travis CI environment it's sometimes frustrating when you make a mistake and then have to wait for the entire commit process to run through before you can try your next build. It would be nice if it were easier to test Travis CI builds locally when initially developing the build. **Recommendations to others considering Travis CI:** Start with a basic .travis.yml file to get your continuous integration going. After that there are a lot of options in .travis.yml. Make sure you check in from time to time to see what is offered. **What problems is Travis CI solving and how is that benefiting you?** We have a popular open source application that is run on a variety of web servers. We use Travis CI to automatically run our unit tests against the various deployment environments. We use it to test pull requests before they are merged into the master branch. We use it to test against new versions of server software before we deploy it on our infrastructure. Our main use of Travis is to have a company-wide check to make sure our software is always correctly building. ### 10. Beautiful interface for CI deployment details **Rating:** 5.0/5.0 stars **Reviewed by:** Ryan B. | Senior Software Engineer III, Enterprise (> 1000 emp.) **Reviewed Date:** March 09, 2016 **What do you like best about Travis CI?** Compare to other services for CI (jenkins, go), personally I find the interface to be cleaner and more intuitive. They have great documentation, and customizing each project with a yaml file in the repo is extremely easy. **What do you dislike about Travis CI?** Over the many years I have been using Travis, I have not experienced anything i dislike. **Recommendations to others considering Travis CI:** Make sure to read through the documentation. There is likely a lot of features you don't know about that can greatly increase your benefit from Travis. **What problems is Travis CI solving and how is that benefiting you?** Being able to monitor and automate deployments is the most beneficial part of software development. Travis does a great job with live feedback and keeping logs of failures to reference in the future ### 11. Almost perfect CI system that still can not test for windows **Rating:** 4.0/5.0 stars **Reviewed by:** Swadesh S. | HGA, Insurance, Enterprise (> 1000 emp.) **Reviewed Date:** December 19, 2015 **What do you like best about Travis CI?** The testing framework looks rock solid, it will add itself to github hook when turning tests on from travis interface. Just a push and it starts building the project. As the outputs are directly copied over from console, errors can easily be tracked. Allows root access so that is a plus. Dependencies can be cached so build times are reduced. Travis even gives you a neat icon to put anywhere to show build status. The web interface shows who last committed, i.e. who caused this build to run, build status for diff. branches and build history. It is a minimal ui approach that also does not eclipse information. Emails me with the build status. **What do you dislike about Travis CI?** Slow builds. Sometimes builds take ages to actually run, so much that I start to mash refresh the page. Still not platform independent, for windows, you have to look somewhere else. It runs ubuntu 12.04 so the packages aren't always updated and have to install them using travis config. dependency directive. Testing on a specific linux like RHEL (for me) could come handy as one that might not fail on ubuntu can fail on RHEL (apt and yum). For fairly standard builds, .travis.yml config is quire easy but anytime Imove to something that is not officially supported, I have to manually manage the dependencies. **Recommendations to others considering Travis CI:** Make sure you have a supported language and build framework, the first setup will be way easier this way and will not scare you away. Builds can be configured to your heart's desire but READ THE DOCS first. **What problems is Travis CI solving and how is that benefiting you?** Testing scripts for work is much easier now that I do not have to deploy in a VM running locally and configure it to notify. ### 12. Beautiful and simple interface, fast builds, deep integration with GitHub **Rating:** 4.0/5.0 stars **Reviewed by:** Jonathan Y. | Senior Software Engineer - OpenShift, Computer Software, Enterprise (> 1000 emp.) **Reviewed Date:** December 17, 2015 **What do you like best about Travis CI?** Creating a build is very simple and consists of checking in a simple YAML file, which contains instructions for build steps. All commits to the master repository as well as any branches or pull requests are automatically built, with a check summary added to on the appropriate pull request, so that you know the code has run through all the tests successfully before merging. Builds themselves are very fast (owing to the container-based architecture if sudo is not required) and there is a wide range of available software (other software can be installed in the Ubuntu Linux images using APT), or else pulled from S3. The user interface is extremely simple and Travis-CI is free for open source projects that are published on GitHub. **What do you dislike about Travis CI?** At the moment, Travis-CI doesn't have support for Windows (this was a key strategic opportunity for AppVeyor). Unfortunately, this means cross-platform builds will be very fragmented (duplicated build configurations have to be present in both travis.yml and appveyor.yml). The Mac support is not completely seamless, because the list of available software on the machines is different (and obviously Mac doesn't support APT). It's unclear whether these are really solveable problems in general, since it's natural that there will be differences between platforms. **Recommendations to others considering Travis CI:** If you have an open source project on GitHub, it's practically a no-brainer, though you'll likely have to combine it with AppVeyor for cross-platform builds. Other options include Circle CI and Drone.io, both of which offer free builds for open source projects. All of these have nice build status badges that can be added to your README. **What problems is Travis CI solving and how is that benefiting you?** Continuous integration builds for open source projects. The key benefit is that Travis CI provides free builds, notifications, and reports/dashboards for open source projects. ### 13. Good enough for a CI, some features missing **Rating:** 3.5/5.0 stars **Reviewed by:** Tauseef R. | Small-Business (50 or fewer emp.) **Reviewed Date:** December 14, 2015 **What do you like best about Travis CI?** I have been using it for only for a few weeks and the best thing is the ease of use of the travis.yml file, my framework/language is well supported, mind you. It works very well with my ruby projects and good enough with c++. The web-ui is nice enough that builds can be tracked easily. Also a good thing, the badge that can be included anywhere (most commonly in github readme.md) to track most recent build status. Another good thing is the github hook, as with every push build is triggered automagically. **What do you dislike about Travis CI?** Language support. One, it did not support vala projects so that was it. Two, for c++ projects to use c++11 with g++ or clang, you have to jump through a lot of hoops, change your travis.yml file and wait for something to break. Another big problem is the wait time, it takes a LOT of time for the build to start after making the latest push, this is where appveyor is better. So, if you are using travis as your only test system, don't. Windows support is also not present currently so that's a problem for VS projects. **Recommendations to others considering Travis CI:** Travis is one of the most popular CI systems out there. Although not as easy as one click, one can easily set up a project to use travis in well under an hour, for well supported systems. I recommend setting up a small test project to try it. If travis meets your specs, then go for it as it is well integrated. **What problems is Travis CI solving and how is that benefiting you?** The need to state build status explicitly in every push is gone. I can simply push to github and it will let others browsing my project know if this version is usable or if they have to revert to a previous release. ### 14. Must-have tool for *any* software project **Rating:** 5.0/5.0 stars **Reviewed by:** Marco P. | Technical Trainer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Travis CI?** Clear configuration specification, wide user community, fast support and updated software in the stack. In addition to that, travis-ci has been a major contributor to the growth of the github ecosystem and to its community: they simply kicked out a free tool that did what an open source project could never afford to help. Some of the project even sponsored travis-ci just because of the major involvement it had in helping the open source software folks. In addition to that, defining matrices of supported software versions is quite easy, compared to (for example) setups like Jenkins-CI, where setting up such a matrix requires a lot of experience and time/resources. **What do you dislike about Travis CI?** Console output in travis-ci is not streamed, but rather "downloaded" to the client, which makes scrolling through large logs a bit painful, and sometimes causes travis-ci to "force" the download to a .txt file instead **Recommendations to others considering Travis CI:** Get started and follow few major repositories in how to set it up: travis-ci is a good tool, but like every tool far from perfect. **What problems is Travis CI solving and how is that benefiting you?** Travis-CI is CRITICAL to software quality and long term support. Without a tool like Travis-CI, no guarantees about software quality can be given, as software upgrades are a moving target. Basically, if you cannot prove that your software works over a quite big amount of different environments, then you cannot prove that it is stable, well supported or working at all. ### 15. Easy integration with github for automated build test **Rating:** 4.5/5.0 stars **Reviewed by:** Sushanth R. | Small-Business (50 or fewer emp.) **Reviewed Date:** April 20, 2016 **What do you like best about Travis CI?** Travis CI services also allow me to do things with GitHub (with access to the Status API, support for branches and pull requests, and automatically setting up from a list of repos) **What do you dislike about Travis CI?** .travis.yaml file little bit confusing, rest every thing works great **Recommendations to others considering Travis CI:** 1) Travis CI runs tests for every push made on github 2) Travis CI runs tests on every pull request from other contributors **What problems is Travis CI solving and how is that benefiting you?** Each commits in my github leads to a test build and if that fails you get notified to email. ### 16. The best hosted CI service available **Rating:** 5.0/5.0 stars **Reviewed by:** Eduardo S. | CTO, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Travis CI?** I love the ease of use, the UI is very simple and well thought out, and it is still powerful enough. **What do you dislike about Travis CI?** I think they could have a personal plan, or at least allow personal accounts to have one private repo integrated for free. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $129 a month for it. **Recommendations to others considering Travis CI:** Travis CI is the best hosted CI service I have tried so far, I've tried several ones and non comes close to their level. The fact that most open source projects are using them should be validation enough. **What problems is Travis CI solving and how is that benefiting you?** Automatic build of all pull requests so we can be sure all tests are passing before we start code review. Continuous integration of our projects, testing and automatically deploying upon succesfull merge of pull requests onto our master branches ### 17. Automated testing for the uninitiated **Rating:** 5.0/5.0 stars **Reviewed by:** Aster H. | Owner, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** January 22, 2016 **What do you like best about Travis CI?** Travis CI made it super simple to integrated automated testing into my Github repos. Auto login, auto-syncing, auto-run mocha testing, container support, content deployment, it handles everything I need it to gracefully and efficiently. **What do you dislike about Travis CI?** The queues can get backed up sometimes, where a new job can be waiting upwards of 5-10 minutes to run. There isn't necessarily a mechanism in place to notify you when something like that occurs, or if there is, I haven't found it yet. **Recommendations to others considering Travis CI:** Read the docs, this tool can do a whole lot if you know what it can do. **What problems is Travis CI solving and how is that benefiting you?** We needed a tool to run automated Mocha tests, trigger BrowserStack e2e tests, and upon success deploy the assets to the domain. It does those jobs wonderfully. ### 18. A great software to check my code **Rating:** 5.0/5.0 stars **Reviewed by:** Krzysztof G. | Small-Business (50 or fewer emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Travis CI?** I'm using Travis CI to check all my pull request. When someone is going to contribute my project I immediately know that everything is ok and it's safe to accept it. When there are any problems I can simply reject a pull request without wasting my time to check it manually. **What do you dislike about Travis CI?** Since I'm not an advanced user I didn't notice any disadvantages yet. **What problems is Travis CI solving and how is that benefiting you?** I'm using it primairly to check the code correctness. It's rather an experiment with using that kind of tools. ### 19. Test, deploy, take a cup of coffee. **Rating:** 4.5/5.0 stars **Reviewed by:** Ramón L. | Analista de Sistemas, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** February 10, 2016 **What do you like best about Travis CI?** With TCI you have a nice way of being aware of what you are building, you can test your code at the same time you deploy, get detailed information about what is wrong(if it is) and saves you a lot of time. The best part is that it's as free as github (This meaning you only have to pay when using private repositories). TCI is definately empowering open source projects with testing and confidence. **What do you dislike about Travis CI?** There's nothing much to dislike about TCI. The only complaint would be the interface, i believe it's too grey and sometimes i get lost with the buttons, but hey, that could be just me. **Recommendations to others considering Travis CI:** Get to know what Travis CI has to offer to you. If you are into TDD, it will be easy to implement. On the other hand i recommend to first learn some TDD before trying Travis CI. **What problems is Travis CI solving and how is that benefiting you?** Getting the testing and deployment phases together into one process speeds up the workflow and gets things going on teams with a high level of work. ### 20. TravisCi Is a very great product. For open source and private projects. **Rating:** 5.0/5.0 stars **Reviewed by:** Benjamin L. | Développeur, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Travis CI?** Travis has a very nice integration with Github. There are aware of new technological changes, before PHP7 was released we can use RC version. It easy to launch test in parallels. When I was student I was eligible to have 1 private repository for free. The support is great and fast. **What do you dislike about Travis CI?** When they migrate to a docker infrastructure, I was experiencing some big issues with build that was not triggered and random errors. Sometime the web site is unusable or there are missing information in the UI. There is no good support for docker. I want to be able to test with specific docker / docker-compose version. **What problems is Travis CI solving and how is that benefiting you?** I'm a developper and I want my workflow to be a maximum automatic. With travis-ci pro I was able to have my test suite executed in 30 minutes instead of 6 hours. ### 21. open source developper review **Rating:** 5.0/5.0 stars **Reviewed by:** Mathieu R. | Lead developper, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** May 18, 2016 **What do you like best about Travis CI?** it's free for open sources projects, very easy to use, integrate very well with a lot other tools & services **What do you dislike about Travis CI?** it's not open source and was a bit slow to upgrade languages version. that's mostly solves and not much of a problem thanks to docker **What problems is Travis CI solving and how is that benefiting you?** running test for repository code and pull requests on different version of languages/tools/OSes ### 22. FOOS review **Rating:** 4.0/5.0 stars **Reviewed by:** Guillaume M. | Consulting Engineer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** March 08, 2016 **What do you like best about Travis CI?** It's free for open source. It's simple to get started and to use. The integration with Github is pretty solid. **What do you dislike about Travis CI?** Limited support for open source in terms of memory. Does not support windows. I use http://www.appveyor.com to fill the gap. However it is pretty slow. My project takes 15 minutes to build and test on AppVeyor and 5 minutes on Travis. **Recommendations to others considering Travis CI:** Offer a premium version (paid) for large open source project which require more memory/cpu usage ex: github.com/typelevel/cats Fix this issue: https://github.com/travis-ci/travis-ci/issues/2317 **What problems is Travis CI solving and how is that benefiting you?** I need a CI system for my open source project: https://github.com/MasseGuillaume/ScalaKata2 ### 23. For me TravisCI is best tool to run tests and deploys **Rating:** 5.0/5.0 stars **Reviewed by:** Fabio d. | Technical Lead Developer, Apparel & Fashion, Enterprise (> 1000 emp.) **Reviewed Date:** December 12, 2015 **What do you like best about Travis CI?** Well, TravisCI for me, is a group of tools that help us to maintain and make our software better, and create possibilities to integrate with another best tools. (Like Github). During use I don't have any kind of problem with this tool, and in all the moments TravisCi help me to create your config file in your faq page, then I will continue using. **What do you dislike about Travis CI?** I don't have any kind of problem when I use TravisCI, for me is the best tool. **What problems is Travis CI solving and how is that benefiting you?** Actually my company use TravisCi with our open repositories in Github, and one that thing that help us is the toolset for PHP, and with that, help us to create better softwares easily. For us the time to develop something is very important, and TravisCI help us a lot. ### 24. Fast and Easy to use **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Mining & Metals | Mid-Market (51-1000 emp.) **Reviewed Date:** May 18, 2016 **What do you like best about Travis CI?** It takes less than a minute to get hooked up with Travis CI and it requires no environment setups. **What do you dislike about Travis CI?** Sometimes it takes more time to get feedbacks if the build is broken. But overall it is pretty fast. **Recommendations to others considering Travis CI:** Try to use it with small and simple projects first to get to know how the system works. **What problems is Travis CI solving and how is that benefiting you?** Travis takes care of running our builds and trying our pull requests before we try to see if they fail a test. It really boosts up our development and management speed. ### 25. The best CI platform **Rating:** 5.0/5.0 stars **Reviewed by:** John V. | Research Data Analyst, Higher Education, Enterprise (> 1000 emp.) **Reviewed Date:** December 18, 2015 **What do you like best about Travis CI?** Travis-CI provides an extremely powerful platform for continuous integration. The .travis.yml build control file is extremely versatile. **What do you dislike about Travis CI?** Travis-CI does not allow build artefacts to be downloaded from Travis-CI. It is necessary to push them to another service, such as S3. I wish they had support for more commercial databases, like Oracle and SQLServer. Also their OSX platform isnt mature and well supported. **Recommendations to others considering Travis CI:** Use it! Use the API. Use tools that exist, such as https://pypi.python.org/pypi/travis_log_fetch Build new tools for it. **What problems is Travis CI solving and how is that benefiting you?** I mostly use Travis-CI for Python development. The obvious benefit is stability, however it also speeds up development processes (coding, code review, deployment) as proposed changes can be verified against a large number of diverse configurations on Travis, catching unintended side-effects. ### 26. Travis provides me a way to develop fast software **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Program Development | Small-Business (50 or fewer emp.) **Reviewed Date:** January 15, 2016 **What do you like best about Travis CI?** Travis is a software that provides me a way to make software without loosing time and with a best performance and quality **What do you dislike about Travis CI?** Travis tends to have a low performance with some test when you're trying theme in the cloud instead using it in local machine **Recommendations to others considering Travis CI:** First you need to consider the requirements of your software, also the enviroment of development and the type of software are you developing, although Travis CI offers a variety of solutions you need to consider all of factors to take advantage of it. **What problems is Travis CI solving and how is that benefiting you?** Travis is solving a continuos integration software problem to my business, its provides a fast way to improve our software and to deliver free bug software to our client, also provides me a way to test it in the cloud, yo share with other partners and also to test in another enviroment. ### 27. Travis CI with open source development **Rating:** 5.0/5.0 stars **Reviewed by:** Matt G. | Senior Drupal Consultant, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** December 12, 2015 **What do you like best about Travis CI?** TravisCI allows for speedy development of open source projects by easily integrating with GitHub and testing changes. With multiple environment support, we can test different languages and environments. We can also test upgrade process to ensure end-to-end satisfaction for users. There are also build caches which allow each subsequent environment build to re-use cached items, such as downloaded dependencies. **What do you dislike about Travis CI?** Setting up the .travis.yml can be tricky and require a lot of useless commits to getting a build working properly. **What problems is Travis CI solving and how is that benefiting you?** TravisCI allows us to run lengthy behavior driven tests without hindering the development time. A typical test may take an hour for one environment setup. Travis CI allows changes to be tested while continuing to develop on other problems. ### 28. Using travis as your automated build service **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** March 10, 2016 **What do you like best about Travis CI?** Travis CI subscriptions let use execute concurrent build jobs across multiple projects. The open source free plan solution is pretty useful as you typically don't need to have a build run immediately although as a company, having multiple concurrent build jobs saves time and resources. **What do you dislike about Travis CI?** UI sometimes makes it difficult to navigate to specific builds and navigate through build history. **Recommendations to others considering Travis CI:** If you are an open source group, you definitely should set up Travis CI. And if you can afford it, you should upgrade to a paid plan to use Travis. Especially since it's really easy to set up. **What problems is Travis CI solving and how is that benefiting you?** We needed a private CI for tests. ### 29. Standard goto for testing open source projects **Rating:** 3.0/5.0 stars **Reviewed by:** Ben E. | Director/Software Consultant, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** December 12, 2015 **What do you like best about Travis CI?** Easy to use and and free for open-source projects. Can test across a wide magnitude of versions/technologies by using Travis Matrices. Saves developers time by running large test suites on a remote system so developers can continue doing what they do best without halting to wait for their own machinery to run the test suite. **What do you dislike about Travis CI?** Builds can take a while to start however their new container-based infrastructure is aiming to fix this issue. Limited to just GitHub repositories. **What problems is Travis CI solving and how is that benefiting you?** Testing software in accordance to GitHub Flow to check pull-requests before merging into the master branch. Assures quality and in accordance with code coverage and maintainability monitoring services can accelerate software development. ### 30. Excellent CI with seamless Github integration **Rating:** 5.0/5.0 stars **Reviewed by:** WEI CHEN L. | Assistant Programmer, Marketing and Advertising, Small-Business (50 or fewer emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Travis CI?** Unbeatable integration with Github and good performance **What do you dislike about Travis CI?** The fact that it only works with Github, the initial setup also requires some useless commits to get the build script working **What problems is Travis CI solving and how is that benefiting you?** Opensource software testing; it's nice to know your project builds on another computer ### 31. Easy to start and need more document **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Animation | Small-Business (50 or fewer emp.) **Reviewed Date:** April 14, 2016 **What do you like best about Travis CI?** easy to start travis ci. If we only write .yml file and upload repository to github, we can get the result of a build. **What do you dislike about Travis CI?** there isn't much document about customized ci. For example , deployment of achievement of the build is difficult for me. I think we need much document about the customization of ci.. **Recommendations to others considering Travis CI:** Easy to start travis ci. building project is very easy **What problems is Travis CI solving and how is that benefiting you?** ci makes our development faster ### 32. Simple and easy **Rating:** 5.0/5.0 stars **Reviewed by:** Aashrai R. | android developer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Travis CI?** Ease of use, its extremely easy for beginners **What do you dislike about Travis CI?** Android Support is okay but really slow, need to provide a custom faster solution for android **What problems is Travis CI solving and how is that benefiting you?** The biggest benefits were care free git pushes ### 33. An excellent build system for open source projects **Rating:** 5.0/5.0 stars **Reviewed by:** Daniele C. | Software Developer, Financial Services, Mid-Market (51-1000 emp.) **Reviewed Date:** December 15, 2015 **What do you like best about Travis CI?** I love the way build logs are displayed, with a clear list of executed commands and collapsable output. YAML configuration is easy to set up and allows me to specify minimum version of PHP and optional versions or languages, like release candidate of PHP 7 or HHVM. **What do you dislike about Travis CI?** Sometime the build just fail due to external errors, like network connection, but it's reported like a code problem. **What problems is Travis CI solving and how is that benefiting you?** I use it for open source projects. Automated tests allow me to accept pull requests without deep code reviews in short time. ### 34. Super easy to use and extremely intuitive. **Rating:** 5.0/5.0 stars **Reviewed by:** Simeon I. | Software Developer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** January 26, 2016 **What do you like best about Travis CI?** The GitHub/Slack integration. I managed to set it up in 5 minutes. The look is also great I can navigate very intuitively. **What do you dislike about Travis CI?** It's not very easy to get the JDK install Dir in a build slave. This is the only negative experience I've had so far. SO question here: http://stackoverflow.com/questions/30832526/get-the-jdk-install-dir-in-a-travisci-build **What problems is Travis CI solving and how is that benefiting you?** We use it for continuous integration. ### 35. Continuous Integration for the 21 century **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Internet | Small-Business (50 or fewer emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Travis CI?** Integration of TravisCI with github, bitbucket, gitlab, and not using jenkins :) **What do you dislike about Travis CI?** It's horrible slow, even when paying, I know there are some challenges to solve in order to make it faster. It would be nice to make a tool for checking the syntax for the .travis.yml one who can check if you didn't had typos like matrxi instead of matrix, and stuff like that, several times sents commits with typos and I believe this would help to down the load in useless builds (useless in the sense that if the syntax is wrong its gonna fail) **Recommendations to others considering Travis CI:** Try it, stop using jenkins! **What problems is Travis CI solving and how is that benefiting you?** Getting test coverage to applications and libraries that I develop ### 36. Fast and highly customizable continuous integration tool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.) **Reviewed Date:** March 14, 2016 **What do you like best about Travis CI?** The fact that it is directly interfaced with Github. **What do you dislike about Travis CI?** The slow installation at each build, maybe it would be better to have a quicker cache or something. **What problems is Travis CI solving and how is that benefiting you?** Continuous testing and publishing to npm. The benefits are that you configure once, then you don't pay attention anymore, you are sure your package will be published if the tests pass. ### 37. Great for testing pull requests **Rating:** 5.0/5.0 stars **Reviewed by:** Ryan G. | Software Developer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** May 25, 2015 **What do you like best about Travis CI?** I really like the automated continuous integration that this system provides. It provides a very seemless integration with Github's continuous integration api. **What do you dislike about Travis CI?** The setup took a little getting used to. I had a hard time understanding the documentation. Once I started to understand the concepts, things went much smoother. **Recommendations to others considering Travis CI:** It was a little difficult for at first because it was the first time I had ever dealt with continuous integration. After getting it setup, it worked beautiful with minimal maintenance. **What problems is Travis CI solving and how is that benefiting you?** We needed a way to test pull requests on Github for a project that I was working on. A friend introduced me to travis ci and it turned out to work very well for our use case. Our project was a small project with multiple developers of varying experience. Things would often be broken by the more inexperienced developers, get merged into the master branch and suddenly everyone was disgruntled. They were usually small errors, but happened frequently. Using Travis CI, we hooked it up with Github to automatically build every pull request to our project. This eliminated almost all of the issues we were having. We could easily see if a build passed or not and then inspect the output. ### 38. Open source **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** December 14, 2015 **What do you like best about Travis CI?** They have a pretty clean user interface that allows me to switch between projects and builds. The fact that they open sourced some of their components helped me in understanding how their platform works and the recent support to docker containers helped me a lot since our infrastructure is based on it. **What do you dislike about Travis CI?** build environment are debian like and I usually have a few issues converting my rhel commands into debian ones. **What problems is Travis CI solving and how is that benefiting you?** We didn't want to manage an in house CI server, Travis helps us in solving that problem ### 39. The standard de-facto **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** January 25, 2016 **What do you like best about Travis CI?** Great UI A simple hidden configuration file to setup your project **What do you dislike about Travis CI?** Nothing much, actually you can get more speed just by paying :) **What problems is Travis CI solving and how is that benefiting you?** Continuous Integration for my open-source projects. I can be sure that every revision I push passes the test and so the pull requests before I have a chance to merge them. ### 40. Went from "would be cool to use" to "vital for our group" in under a month **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** January 25, 2016 **What do you like best about Travis CI?** Its really simple to get started with and how it integrates so seamlessly into github is a real selling point. **What do you dislike about Travis CI?** Sometimes its slow, however its most likely due to external services. **Recommendations to others considering Travis CI:** If your on github you have no reason not to try it. **What problems is Travis CI solving and how is that benefiting you?** Continuous integration and automated testing and feedback ### 41. Travis CI is awesome! **Rating:** 5.0/5.0 stars **Reviewed by:** Kasparas G. | Web Developer, Marketing and Advertising, Mid-Market (51-1000 emp.) **Reviewed Date:** May 11, 2015 **What do you like best about Travis CI?** The new interface is very slick. I love how easy is to use your product - configuration, monitoring builds, that little button that allows you to follow the log etc... It's really cool! Also, the fact that it's built in Ruby (or maybe a part of it) makes me like this product even more! **What do you dislike about Travis CI?** I would like to be able to: * SSH to the build machine to debug a build failure * Ability to manually trigger a new build * Ability to re-arrange/re-prioritise the builds **Recommendations to others considering Travis CI:** Don't consider it - just use it. It's great! **What problems is Travis CI solving and how is that benefiting you?** All of our apps are being built on Travis CI, packaged up and deployed to our servers. Being able to see if our pull requests pass before a merge was a great benefit to us when we started using Travis. ### 42. Simple, battle-tested continuous integration for your Open-source needs **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** May 04, 2015 **What do you like best about Travis CI?** Simplicity: create a .travis.yml file in your project to set up configuration, build and test your github project, and use your Travis-CI account to activate a github project of yours. With every commit, Travis-CI creates a new VM instance, checks out your latest code, and runs the instructions in your .travis.yml file. Good documentation and free service! Outputs are streamed live, supports many languages, with slack chat integration. **What do you dislike about Travis CI?** Unstable at times. When compiling or running tests, it will hang up for unknown reasons requiring manual intervention. Most of the time this issue does not happen but occurs occasionally. **What problems is Travis CI solving and how is that benefiting you?** As a hosted continuous integration service for the open source community, it is very useful to modify and not-very-difficult to set-up. It's well-known status amongst the open-source community make it easy to find help so the business problem of finding more knowledgeable people isn't an issue. I've realized that it supports multi-version builds. If you want to test your codebase against every combination of every version of Python and Django, Travis can do this. And they make it really simple. Travis is mature and has been around for a lot longer, it is battle tested, and is used by many important open source projects. ## Travis CI Discussions - [[Hosted] Are there any restrictions on build time?](https://www.g2.com/discussions/hosted-are-there-any-restrictions-on-build-time) - 1 comment, 1 upvote - [Why choose Enterprise over travis-ci.com?](https://www.g2.com/discussions/why-choose-enterprise-over-travis-ci-com) - 1 comment, 1 upvote - [[On-prem] What are the features of Travis CI Enterprise?](https://www.g2.com/discussions/on-prem-what-are-the-features-of-travis-ci-enterprise) - 1 comment, 1 upvote - [[Hosted] What is a concurrent job?](https://www.g2.com/discussions/what-is-a-concurrent-job) - 1 comment, 1 upvote - [[On-prem] Why choose Travis CI over Jenkins?](https://www.g2.com/discussions/why-choose-travis-ci-over-jenkins) - 1 comment, 1 upvote - [View Travis CI pricing details and edition comparison](https://www.g2.com/products/travis-ci/reviews?page=2§ion=pricing&secure%5Bexpires_at%5D=2026-07-17+04%3A35%3A43+-0500&secure%5Bsession_id%5D=69e0f20f-ea8b-4499-a98d-14dda8053fd2&secure%5Btoken%5D=a8e307c3b1f4f99d62b6746036f4694c811d7e03627582468f721d26de380f7e&format=llm_user) ## Travis CI Features **Functionality** - Deployment-Ready Staging - Integration - Extensible **Functionality** - Integrations - Extensibility - Test Customization **Management** - Processes and Workflow - Reporting - Automation **Management** - Automation - Processes and Workflow - Reporting **Agentic AI - Continuous Integration** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance **Agentic AI - Continuous Delivery** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance ## Top Travis CI Alternatives - [Jenkins](https://www.g2.com/products/jenkins/reviews) - 4.4/5.0 (557 reviews) - [CircleCI](https://www.g2.com/products/circleci/reviews) - 4.4/5.0 (499 reviews) - [Azure DevOps Server](https://www.g2.com/products/azure-devops-server/reviews) - 4.2/5.0 (192 reviews)