# 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. Automated built and test pipelines - travis CI **Rating:** 4.0/5.0 stars **Reviewed by:** Aniruddha H. | Software Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** September 08, 2023 **What do you like best about Travis CI?** The best thing I like about Travis CI is its simplicity and user-friendliness. In Travis, setting the CI (continuous integration ) pipeline is so smooth and simple. **What do you dislike about Travis CI?** The downside of Travis CI is it is very slow; it takes a long time to show results after every code is pushed to the repository. its interface is not so good either. **What problems is Travis CI solving and how is that benefiting you?** Travis CI helps us automate the test process; every time you push code in the repositories it is testing it. It helps in CI ( continuous integration ) and it blends with Github very easily. ### 2. Travis CI/CD Integration - Make it easy **Rating:** 4.5/5.0 stars **Reviewed by:** Vijay P. | Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** March 09, 2024 **What do you like best about Travis CI?** The best that I like about Travis CI which helps to validate the code after the deployment cycle and which points out the break of interruption in a code without other functionalites of a code **What do you dislike about Travis CI?** Build process will take some time, and integration with GitHub will have some cache issue. **What problems is Travis CI solving and how is that benefiting you?** Travis CI is beneficial in maintaing the coding standard and prevent our application from error during the deployment process. ### 3. #1 cloud based CI/CD solution widely used for enterprise applications **Rating:** 4.5/5.0 stars **Reviewed by:** Mansi M. | Software Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** November 27, 2022 **What do you like best about Travis CI?** I like the best that it is a commercial CI tool, excellent for enterprise applications. It takes very little time to set up and it provides a high-quality CI/CD platform which increases the application's productivity. Some of its best features are automating the builds while creating pull requests and can be easily integrated with different version-management applications. Additionally, it provides very clear and concise errors in the builds, which helps developers fix the issues very quickly and efficiently. I can easily automate tasks like tests, integration and deployment. **What do you dislike about Travis CI?** I do not like it, when compared to the open-source tool Jenkins, it provides little fewer customization options. This is because of the simplicity offered by the Travis tool. But, overall, the setup and pricing is excellent. **What problems is Travis CI solving and how is that benefiting you?** It helps teams automate their project's build and identify any bottlenecks before merging code for production use. It also allows developers to hook up test classes, coverage, code smells, etc. in the continuous pipeline. Moreover, its integrations with third-party apps are very seamless, like with Hashicorp Vault, Code Climate, and Sonar Qube. ### 4. A tool that makes pipeline automation easy to go **Rating:** 5.0/5.0 stars **Reviewed by:** Juan M. | Operations Agile coach, Mid-Market (51-1000 emp.) **Reviewed Date:** November 07, 2022 **What do you like best about Travis CI?** Travis is a very practical service to automate pipelines, it's based on standard technologies and provides robust integration support with any other cloud provider. From a technical perspective. **What do you dislike about Travis CI?** Building automation in a cloud-based service implies the latency of moving things over the internet so depending on the size of the build one could feel it takes time. I find the logs feature simple in the end it fulfills its purpose but a smarter tool would add more value. **What problems is Travis CI solving and how is that benefiting you?** Pipeline automation for various react and node-based web apps, integrated with AWS and GCP workloads, I believe Travis does great with these integrations and many other services along the way as github, 1password, cloudWatch, eks, etc. ### 5. One of top CI/CD agnostic platform **Rating:** 4.0/5.0 stars **Reviewed by:** Joel L. | Lead Developer & Founder, Small-Business (50 or fewer emp.) **Reviewed Date:** December 04, 2022 **What do you like best about Travis CI?** The way to build CI workflow is so simple, useful **What do you dislike about Travis CI?** The cost of platform for small business budget **What problems is Travis CI solving and how is that benefiting you?** Travis CI is helpful for CI, it offers more integration with other code platforms ### 6. Great cloud solution for Continuous Integration and Deployment **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** January 22, 2022 **What do you like best about Travis CI?** - Excellent cloud-based solution for CI/CD without having to self manage the build server and build agent - Build and deploy scripts as code in travis.yml file - Easy integration with GitHub - Dependency setup is easy in Travis with configurations (eg- node, java, ruby, docker etc) - Ability to ssh into build agents for troubleshooting build and deploy issues - Build matrix feature is great **What do you dislike about Travis CI?** - No support for account level environment variables (e.g.- AWS user credentials or artificatory user credentials must be managed in individual repositories) - No provision for running in private VPC (e.g- Accessing database hosted in private VPC to run migrations) - No auto mechanism to invoke dependent builds in another project - Would be good to have some sort of metrics around builds (historical build execution time, build failure rate, etc.) **What problems is Travis CI solving and how is that benefiting you?** Travis CI mainly helps us quickly build and deploy applications without the overhead to maintain build servers and agents. Having build and deploy scripts as code brings in transparency and allows us to test and make changes quickly. ### 7. For easy CI, DevOps without much configuration Travis CI is best **Rating:** 4.0/5.0 stars **Reviewed by:** Karur S. | System Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** October 27, 2021 **What do you like best about Travis CI?** AutoSync with Git and bitbucket. Easy integrations for AWS, HEROKU, and other cloud platforms and technologies. Also, the logging system while performing unit tests and live builds helps a lot when debugging errors. **What do you dislike about Travis CI?** Pricing is very expensive, even for starting with basic pricing plans. **Recommendations to others considering Travis CI:** More flexible pricing plans and simultaneous builds features are very helpful. **What problems is Travis CI solving and how is that benefiting you?** It makes my job easy to deploy and test various types of applications with easy integration. Conditional builds is very helpful feature which allows deployments to production occur only when commits to master branch occur. ### 8. Best CI tool for starters **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** May 11, 2021 **What do you like best about Travis CI?** Travis is easy to use. If your project is open source in GitHub then you can try Travis for free, and you can purchase the service only when you are ready to use it for private repositories. The configuration file is written in yaml, so it is very easy to use for starters. Also, you can use docker images easily. **What do you dislike about Travis CI?** The test report is not very clear. For example, there are other CI tools that show test results more clearly. Also, for free service, configuring parallel execution is tricky. **What problems is Travis CI solving and how is that benefiting you?** I have used Travis to run E2E tests. It is free for open source projects, so it really helped me to understand the concept of CI tools. ### 9. Travis CI used to be CI and Automation tool **Rating:** 3.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** November 08, 2021 **What do you like best about Travis CI?** Travis CI is a legacy CI tool, easy to integrate and deploy **What do you dislike about Travis CI?** When too many folks are committing at the same time, it becomes very slow, it struggles during heavy traffic. **What problems is Travis CI solving and how is that benefiting you?** We used it as our CI tool, on every commit it builds our app and run tests and if any of it fails it disables merging of our PR. ### 10. Very good CI Tool to compile in multiple platforms. Excellent documentation. **Rating:** 5.0/5.0 stars **Reviewed by:** Manuel Ernesto G. | Software Development Specialist, Small-Business (50 or fewer emp.) **Reviewed Date:** June 17, 2021 **What do you like best about Travis CI?** What I like most is the option to comply entirely free for open code projects. **What do you dislike about Travis CI?** For users who start trial credits end quite fast above all if they use macOS servers **What problems is Travis CI solving and how is that benefiting you?** I can compile multiplatform applications in the cloud without having to install different operating systems on my machine. All this automatically and integrated with git ### 11. Easy integration **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** November 23, 2021 **What do you like best about Travis CI?** Integrates with github easily and cheaper than other ci/cd tools **What do you dislike about Travis CI?** Limited features but could be the pricing tier we signed up for. Sometimes it crashes **What problems is Travis CI solving and how is that benefiting you?** ci/cd pipeline, spins up docker and catches errors based on unit tests we have. ### 12. Increases code quality by making sure all is saved several times a day **Rating:** 5.0/5.0 stars **Reviewed by:** Ludwig C. | Enterprise (> 1000 emp.) **Reviewed Date:** October 20, 2020 **What do you like best about Travis CI?** When used in conjunction with GIT and any IDE that supports it is very easy to automate tasks of the continuous development pipeline and with that free mental resources to actually work in the idea that you want to implement thru code since you can get notifications whenever something relevant for you is getting changed. **What do you dislike about Travis CI?** In a perfect world, Travis will work on its own without minimal human interaction, and with experienced teams that is usually the case but when dealing with new developers or with those that are not accustomed to the CI/CD pipeline it is kind of not intuitive and takes some time to get used to it. **Recommendations to others considering Travis CI:** It is great to automate tests in any CI/CD project as long as you understand how it works **What problems is Travis CI solving and how is that benefiting you?** It's a great tool if you are building with CI/CD in mind ### 13. Deployments in an automated and integrated manner with various applications. **Rating:** 5.0/5.0 stars **Reviewed by:** Jericsson C. | Analista IT, Small-Business (50 or fewer emp.) **Reviewed Date:** February 15, 2021 **What do you like best about Travis CI?** Continuous integration and rapid deployments with many technologies: Heroku, GitHub, Slack among many others. You can see the operation of the applications in just minutes. Management of repositories and notifications via email. **What do you dislike about Travis CI?** The free version does not have private repositories. **Recommendations to others considering Travis CI:** The paid version offers better response quality at the server level and allows you to set up private repositories for your company. **What problems is Travis CI solving and how is that benefiting you?** Perform FrontEnd and BackEnd testing by integrating applications, seeing results quickly and without complications. ### 14. It's easy to use and save much time for configuration **Rating:** 4.0/5.0 stars **Reviewed by:** Dianne H. | Mid-Market (51-1000 emp.) **Reviewed Date:** August 28, 2020 **What do you like best about Travis CI?** Travis CI is easy to use and save much time for configuration . Travis CI is suitable for the open source , private projects and supports private builds . I used Travis for testing and developing environments . It helped me avoid unexpected issues , encounter and handle the problems such as : bugs and crash. Especially , Travis is easy to interact all information with Github platform . I saved much time with Travis . All is smooth . **What do you dislike about Travis CI?** It sometime takes more time to build . I don't like product design on Travis CI . **Recommendations to others considering Travis CI:** Travis CI helped me save much time for configuration and handling the unexpected issue and bugs , so I think that it's also suitable for you . Worth trying ! **What problems is Travis CI solving and how is that benefiting you?** Travis CI company should improve product design and add more new features . Travis CI should be updated to be suitable with the current technology and development . ### 15. Great CI **Rating:** 4.0/5.0 stars **Reviewed by:** Michael C. | Software Engineer II, Small-Business (50 or fewer emp.) **Reviewed Date:** July 10, 2020 **What do you like best about Travis CI?** Travis works great for CI/CD pipelines. It's easy to configure and has great integrations with tools you are probably already using like github. It's also compatible with many popular languages. **What do you dislike about Travis CI?** Travis has had some outages and strange behavior in the past. Occasionally builds break due to aggressive caching - there might be a way to disable that though. **What problems is Travis CI solving and how is that benefiting you?** We use travis for testing pull requests and running linters. This helps to make sure we do not push broken builds and that everyone is following the same coding guidelines. ### 16. Automate your builds **Rating:** 4.5/5.0 stars **Reviewed by:** hamza a. | iOS Developer, Mid-Market (51-1000 emp.) **Reviewed Date:** October 30, 2019 **What do you like best about Travis CI?** It automate the build process and handle test cases. You can run test cases on mac and linux both at the same time. Configuring travis is easy using lightweight YAML file. We don't need to setup our own server to run it. It also provide free support for public repos. **What do you dislike about Travis CI?** When it comes to private repos the pricing is bit high compared to other providers like CircleCI. Third party integration is needed for configuring customization such as linter etc. **Recommendations to others considering Travis CI:** If you want to make your life easier and save time to automate you build just go for it. It doesn't only automate the builds you can do some cool stuff to maintain you code quality and make sure nothing wrong goes to your prduction builds next time when you release. **What problems is Travis CI solving and how is that benefiting you?** We use it to automate our builds and run test cases. Provide builds to QA team and upload the build to App store. ### 17. Travis CI is easy and ready to be used CI tool in market. **Rating:** 4.5/5.0 stars **Reviewed by:** Tamseel A. | Full-stack Developer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** October 18, 2019 **What do you like best about Travis CI?** Ready and easy to use, you don’t need any extra configuration like other CI tool like Jenkins. simply integrate GitHub or version control system, when ever you push the code its tested and integrated. Multiple jobs allow you to run and test simultaneously on different environment and OS. Free for your public projects, you don’t have to pay for your test and open source projects. You don’t have to maintain hosting server, Travis CI handle and maintain updates and hosting server. Plugin and integration with third party tools are available but its limited. **What do you dislike about Travis CI?** Travis CI is not extensible and high customizable like Jenkins because of its limited plugins and third-party integration. You have to pay for private repositories unlike Jenkins which provide unlimited private repositories. Its not open source which is not good for highly sensitive projects whereas Jenkins is a open source. **Recommendations to others considering Travis CI:** Overall Travis CI is popular and most trusted CI tool available in market. It depends on project whether you have to use it or not. If you are working on project which is not too complex and small or medium scale, then you don’t need to go for extra work for configure just use Travis CI it easy to setup and ready to use. If you are working on large enterprise project which require lot of customization and integration with other tools, then Jenkins would be best choice for your project. **What problems is Travis CI solving and how is that benefiting you?** Travis CI is easy and ready to use Continuous integration and continuous delivery tool available in the market. We have used Travis CI for medium scale project to automate testing, integration and deployment. We also use Travis CI for test and open source projects because it provides free public repository, you don’t have to pay for public projects. We create different jobs for each module which allow to run simultaneously on multiple environment and OS. ### 18. I'm frontend developer with 5 years of experience using Travis **Rating:** 4.0/5.0 stars **Reviewed by:** Luigi Mattia B. | Web Developer, Mid-Market (51-1000 emp.) **Reviewed Date:** April 03, 2020 **What do you like best about Travis CI?** It is easy to implement and it works good with python and react **What do you dislike about Travis CI?** Sometimes it blocks and it is not easy to understand why **What problems is Travis CI solving and how is that benefiting you?** I realize my project with laravel and react and it was good choice ### 19. Great service when building in the cloud **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** April 30, 2020 **What do you like best about Travis CI?** Its fast, flexible and all configuration (except credentials) are store with your source code. **What do you dislike about Travis CI?** It does not support nested virtualization. **Recommendations to others considering Travis CI:** It is very easy to get started as it has very good integration with github. **What problems is Travis CI solving and how is that benefiting you?** CI/CD. All build and deploy operation for my software projects are fully automated and test on multiple platforms. ### 20. Travis Continuous Integration - Way to test your Android / iOS Application **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.) **Reviewed Date:** September 28, 2019 **What do you like best about Travis CI?** -Travis Continuous Integration is a tool for developers to test their pre-released Android or iOS application in possible every environment and device compatibility. - Travis Continuous Integration is open source and also available in paid version. - Travis Continuous Integration help you deploy your test application in various devices compatible with various hardware configurations. - Basically Travis Continuous Integration is testing your test application stored in GitHub Repository doesn't matter that repository is Private or Public and gives you best possible results and help you a lot for solving bugs. **What do you dislike about Travis CI?** - For using Travis Continuous Integration, one should have GitHub account. Person can only sign up in Travis CI using GitHub only. - Travis CI is taking very long time to test application which can be sometime very irritating. **What problems is Travis CI solving and how is that benefiting you?** Before Travis CI, developers of our team was unable to test out product on each and every mobile but after working with Travis CI, we can gave assurance to our clients about compatibility of our product for each and every mobile. ### 21. Necessary tool for CI **Rating:** 5.0/5.0 stars **Reviewed by:** Andrea C. | Web Developer, Small-Business (50 or fewer emp.) **Reviewed Date:** October 22, 2019 **What do you like best about Travis CI?** Simple to use and manage, helps a lot continus integration. It's a must-have! **What do you dislike about Travis CI?** A bit complex for beginners to setup and understand how to write travis.yml. **Recommendations to others considering Travis CI:** Study how it works, and you can easily build, track and manage your software. **What problems is Travis CI solving and how is that benefiting you?** Helps me with CI, i can easily track if a commit has some bug, and i can easily test more language's version in one time. ### 22. Automates tests and project builds **Rating:** 4.5/5.0 stars **Reviewed by:** Ivan A. | I.TOperations, Small-Business (50 or fewer emp.) **Reviewed Date:** September 12, 2019 **What do you like best about Travis CI?** Integration with github open source projects. Every time a push or merge takes place in a git repo that has a travis configuration, tests a run automatically. When the tests complete travis can automatically generate a built and / or deploy the project to a live server depending on your travis configuration. **What do you dislike about Travis CI?** Travis is only free for public github projects, will require a payment plan for private repos. **What problems is Travis CI solving and how is that benefiting you?** Travis C.I ensures that faulty code cannot be merged into a stable version ### 23. One of the best CI solutions out there **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** December 31, 2018 **What do you like best about Travis CI?** It "just works". The build logs can be viewed in real time (live tail). Lots of useful integrations. travis-ci.org is very popular for open source projects so many fellow developers will already be familiar with it. **What do you dislike about Travis CI?** The documentation could be better; there's no reference for the travis.yml file so you have to read/search the full docs to find what you're looking for. The pricing is on the high side. **Recommendations to others considering Travis CI:** Excellent CI solution. Pricing is on the high side but it's worth it when you consider the time saved. **What problems is Travis CI solving and how is that benefiting you?** We use Travis for running tests (automated builds) and continuous deployment. It has standardized our deployment process and saved a lot of time - now we just push to the git repository and Travis takes care of the rest. If there's a build error, it'll let us know via Slack - pretty neat. ### 24. Travis CI Makes Testing and Deploying Easier **Rating:** 5.0/5.0 stars **Reviewed by:** Shazmin M. | Explorer Intern, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** November 23, 2018 **What do you like best about Travis CI?** I really liked using Travis CI when I wanted to deploy changes to the open-source project I was working on - it was very easy to pinpoint which exact tests failed and where I had to go back to fix them before deploying. **What do you dislike about Travis CI?** It takes a very long time to run through the tests for some reason - the project I worked on was fairly small so I wasn't sure why it took 2 - 3 minutes just to run tests (this also slowed down our productivity in general, although I know there were other ways to run tests running it on Travis was visually the best to see what the outputs were). Additionally, even if the tests did all pass, there were still many moments that the tests didn't catch which made our website go down. **What problems is Travis CI solving and how is that benefiting you?** My team used data from libraries from the IT team on campus to find spots on campus that were not being used so users could easily find unused rooms. Our specific project was to predict which spots would be free using past data. The benefits I realized was that deploying was fairly simple. ### 25. One of the best tools I've used to deploy applications **Rating:** 4.5/5.0 stars **Reviewed by:** Israel L. | Coordinador General, Program Development, Small-Business (50 or fewer emp.) **Reviewed Date:** September 26, 2018 **What do you like best about Travis CI?** I knew the tool thanks to the Github platform, it seemed extraordinary the integration that these two platforms have, just by doing 'push' to my repository I could automate validation, integration and deployment tasks with only 1 command. In addition to this you can integrate the tool with Telegram Bot to be aware of the status of the deployment of the application. This is a good tool to use next to github. **What do you dislike about Travis CI?** when you want to do mass deployment process, the configuration becomes a bit complex, since it does not provide tools to perform these processes from the web interface, you must have advanced technical knowledge if you want to achieve good results. **Recommendations to others considering Travis CI:** I recommend this tool to all those who want to automate their development processes and deployment of applications **What problems is Travis CI solving and how is that benefiting you?** Thanks to this tool, the unit testing processes, massive deployment of applications, were automated. The times for deployment to production were reduced. ### 26. Great way to check builds **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** March 18, 2019 **What do you like best about Travis CI?** I like how speedy and accurate Travis CI is. In addition, it’s easy to use and provides a detailed report **What do you dislike about Travis CI?** The pricing and free trial tend to be minimal **What problems is Travis CI solving and how is that benefiting you?** Everyone on my repository can check their builds before a pull request ### 27. Travis-ci makes for painless CI **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Entertainment | Mid-Market (51-1000 emp.) **Reviewed Date:** October 19, 2018 **What do you like best about Travis CI?** Integrating Travis into a project is essentially painless. Create a simple config file and Travis takes care of the rest, even if your app needs to be built via Docker containers or other modern delivery mechanisms. **What do you dislike about Travis CI?** If you have a lot of devs and a lot of projects, sometimes builds will get held up in a queue. **What problems is Travis CI solving and how is that benefiting you?** By switching to Travis we were able to decommission our Home-grown Jenkins infrastructure that nobody on the team really cared to maintain or keep updated. Builds are generally faster and we can more easily have multiple builds at the same time. Having Travis results directly in GitHub makes reviewing pull requests more informative as well. ### 28. Keeping our code honest and consistent! **Rating:** 4.0/5.0 stars **Reviewed by:** Jonathon P. | Website Platform Technical Lead, Mid-Market (51-1000 emp.) **Reviewed Date:** December 19, 2017 **What do you like best about Travis CI?** I like that it is an environment where you can essentially set anything up like you would locally via your terminal. Using Travis CI also keeps everyones code constant with the linter rules in place, and in the beginning helped with learning what in the code needs to be done before deploying it. **What do you dislike about Travis CI?** I dislike that if a Pull Request was not properly merged with the master branch that Travis CI uses to check against it will fail. So if the references don't match it just breaks, but maybe its just my works setup with Travis. Sometimes Travis feels like it takes longer than it should, but I think this is situational. **Recommendations to others considering Travis CI:** Just make sure if you want to use it to build your environment that it meets all the requirements. Basically don't just assume Travis CI is the solution for you. **What problems is Travis CI solving and how is that benefiting you?** We use Travis to keep our code honest. We use it for tests to make sure it passes before deploy. We use it as the middle man. Benefits: Keeps code constitant Catches errors with tests Updates linter rules as per the parent it calls from ### 29. Easy to integrate, useful CI tool **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Apparel & Fashion | Mid-Market (51-1000 emp.) **Reviewed Date:** April 27, 2018 **What do you like best about Travis CI?** It integrates well with GitHub, automatically running tests for new commits, so we don't have to manually ourselves. Forces users to ensure their code is tested before merging with master. The integration is fairly simple with just a configuration file. Granted, if you have a more complex build, this integration can be more complex. Their documentation is fairly extensive though which is good. **What do you dislike about Travis CI?** The UI can be a bit clunky to use and the view for builds could load faster. It also can get pricey for the paid versions for a startup. If you have multiple team mates collaborating, the list of builds waiting can queue up meaning you're waiting potentially hours (if each build takes 30min). **Recommendations to others considering Travis CI:** This tool saves developers a lot of time and ensures higher quality output from an engineering team. I would definitely recommend it and if you have an Open Source project, it's free too. **What problems is Travis CI solving and how is that benefiting you?** We use it mainly for automated tests and continuous deployment for our staging environment. It saves our developers time from handling these tasks that take somewhere between 30-60minutes each time. And instead free them up to be working on other things. It means all code is now always tested routinely without any excuses for lack of time/laziness. ### 30. Travis CI **Rating:** 5.0/5.0 stars **Reviewed by:** Sherif W. | Software Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** May 19, 2018 **What do you like best about Travis CI?** Awesome to run unit and integration tests after each commit and can be used with Github easily with few configurations. **What do you dislike about Travis CI?** Don't have thing to dislike just learn how to configure. **Recommendations to others considering Travis CI:** Try to use it in projects as it makes life easier and not expensive. **What problems is Travis CI solving and how is that benefiting you?** Used to help with build automation after each commit also to run tests as well as helping with deployment. ### 31. They make a better place for open source community **Rating:** 5.0/5.0 stars **Reviewed by:** Igor R. | UI Engineer, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** January 01, 2018 **What do you like best about Travis CI?** Most of the open source libraries use TravisCI - that's what makes TravisCI pretty - love how they support open source community. **What do you dislike about Travis CI?** Had some troubles time ago to set up a private repository - not sure how it's working for private one now on - but it was so complicated awhile ago. **Recommendations to others considering Travis CI:** If you do have an open source library, go ahead and use TravisCI, please do what the most the open source libraries are doing. **What problems is Travis CI solving and how is that benefiting you?** All my open source libraries use TravisCI - just for open source libraries hosted by GitHub ### 32. Better CI for your projects **Rating:** 4.0/5.0 stars **Reviewed by:** Jim Ryan Z. | Software Engineer, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** November 03, 2017 **What do you like best about Travis CI?** Travis has been a very good experience to me compared to using other CI. We went from CircleCI to this because of it's simplicity, the config is very easy and the documentation is really good for the newcomers to using CI's. **What do you dislike about Travis CI?** The UI I think is the weakest part of Travis, compared to some other CI's, it'd lacking in that front, but not in very wide gap though. Something clean and really modern would do. **Recommendations to others considering Travis CI:** Travis CI is one of the best CI's I have ever used. It has great support for web development, is very accessible for new users, has several integrations with other software to make it even better and just overall faster and stabler than any other CI's i have used. The UI though, although satisfactory could be better. **What problems is Travis CI solving and how is that benefiting you?** We use Travis CI as a tool for checking if tests are working before we deploy them. We use it as a measure if a pull request for our application is good for deployment. It also has integration with slack and chrome has been really good overall. ### 33. User Friendly Interface **Rating:** 4.5/5.0 stars **Reviewed by:** Rebecca T. | GED Program Manager | Data Manager, Education Management, Small-Business (50 or fewer emp.) **Reviewed Date:** December 27, 2017 **What do you like best about Travis CI?** It's straightforward to integrate with GitHub. Generally all documentation is clear and easy to understand. **What do you dislike about Travis CI?** Sometimes (4/10 builds) will be stuck on the queue for an extremely long time. **What problems is Travis CI solving and how is that benefiting you?** Travis has been an excelleng "middleman" to ensure that I never submit broken builds to deployment. ### 34. Continuous Integration with Travis **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Research | Mid-Market (51-1000 emp.) **Reviewed Date:** May 16, 2017 **What do you like best about Travis CI?** Travis CI makes it easy to setup Continuous Integration services for projects hosted on Github. For open-source, public projects on Github, the service is completely free (travis-ci.org is for open-source projects, travis-ci.com for commercial). The service allows building and testing with a large variety of supported languages. Using a "build matrix" the code can be tested under different language versions. After a successful build, the code can be directly deployed. Travis works well together with Heroku (heroku.com) for this purpose. **What do you dislike about Travis CI?** With very large test suites or very complex dependencies, builds can sometimes take some time. However, this is in inherent problem with Continuous Integration services, not limited to Travis. **Recommendations to others considering Travis CI:** Free Continuous Integration services for open-source, public repositories hosted on Github. Integrates well with Heroku. **What problems is Travis CI solving and how is that benefiting you?** Travis allows very clearly communicating the current status of a project. Builds are tested on a secondary platform, without any customizations, that is not the developer's machine, preventing the dreaded "works on my machine" problem. The ability to test under different language versions makes uncovering bugs when supporting older versions simpler. ### 35. Travis CI is good **Rating:** 5.0/5.0 stars **Reviewed by:** Erdenezul B. | Senior Software Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** September 28, 2017 **What do you like best about Travis CI?** Travis CI is best continuous integration tools especially you can easily test your product within different environments. **What do you dislike about Travis CI?** I didn't find any bad behavior in this project. **Recommendations to others considering Travis CI:** When you have a software that supports multiple version(python2.6 python3.5 ... etc), Travis Ci is the best for your continuous integration tests. **What problems is Travis CI solving and how is that benefiting you?** Test product easily with multiple environments. (MongoDB v2.6, v3.2, v3.4 etc) ### 36. Not so reliable continuous integration service **Rating:** 3.0/5.0 stars **Reviewed by:** Verified User in Education Management | Mid-Market (51-1000 emp.) **Reviewed Date:** March 07, 2017 **What do you like best about Travis CI?** It has integration with Github's web hooks and with Slack. It's very ease to use and the builds are fast. **What do you dislike about Travis CI?** The service has been very intermittent in the last couple of months and that affects our development workflow. **Recommendations to others considering Travis CI:** You should consider that this service can be very unstable. **What problems is Travis CI solving and how is that benefiting you?** Running tests and developing to stage automatically whenever a commit or a merge is done in Github. ### 37. Simple, powerful and easy to integrate **Rating:** 5.0/5.0 stars **Reviewed by:** Steven H. | Software Engineer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** April 14, 2016 **What do you like best about Travis CI?** I love the integration with Github, when it adds visual information to a pull request to let you see how a build is progressing and what problems it has (if any). I love that it's very easy to configure without any hassle. I love the badge you can put on a website or in your readme to show whether the build is passing or not. I love the fact that it has built-in support to deploy to other vendors, like Heroku **What do you dislike about Travis CI?** Difficult to build native .Net projects without using Mono, but that's more of a disappointment with the .Net build ecosystem and not a fault of Travis as such. Also, pricing - I've only had need to use the free open-source tier, as all the projects I've worked with are open source, but the price of the first paid tier ($129 per month!) is, for me, quite prohibitive and really puts me off making the leap to pay for it. If there was an even cheaper tier, for example one which was say $30 per month with 1 concurrent job and limited minutes per month, but allowed private repositories, then I would probably make that jump. I just feel there's a big gap in the entry-level pricing tiers. **Recommendations to others considering Travis CI:** Give it a try and not be put of by big words like "continuous deployment". It was so easy to use. **What problems is Travis CI solving and how is that benefiting you?** Developing a website for my wedding with another developer. We quickly realised the benefits of Continuous Deployment specifically, and more importantly, how easy it was to set it all up. Everyone should be doing this! ### 38. Travis for Open Source CI **Rating:** 3.0/5.0 stars **Reviewed by:** Mario C. | Army Of One, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** April 13, 2016 **What do you like best about Travis CI?** Travis really shines on their language support as well as capabilities. Its UI is nice, very nice, with a dashboard that allows you to check the status of 6 or 7 projects at the same time (depending on your screen size and resolution) and their status. **What do you dislike about Travis CI?** The real downside of Travis is that you need to add a file to your project to start using it. This is mandatory today and this file can be quite complex. This leads to some "useless" commits just to correct some configuration in this file and check if it works on the Travis dashboard. Once you tweak the file correctly, you don't have problems anymore with it. **Recommendations to others considering Travis CI:** Travis is being used in many open source projects already which is a very good sign. I really like it but today I would prefer to used something like Drone.io for my CI. I haven't introduce CI or CD into my workflow as to take time from my development schedule and Travis fits quite nice (once you configure it correctly). Travis is very well suited for open source projects as it has direct Github support with a simply click so, if you are it the open source community, give it a try. **What problems is Travis CI solving and how is that benefiting you?** I use Travis in my open source personal projects as my main CI workflow. I mainly use it in the most common way: to check unit tests that I have on the project every time I made a push to Github and feel sure that I haven't broken anything. ### 39. Travis CI review **Rating:** 4.0/5.0 stars **Reviewed by:** Csaba K. | Android developer, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Travis CI?** I like Travis CI because it is really simple. All the configuration is in just one YAML file. We can list all the build steps we want in the build lifecycle with simple commands, just like as we do in the terminal. No GUI clicking, building is required. The second best thing is the GitHub integration, which is flawless. You just add the conf file, enable the repo, and you got full integrated CI with your GitHub repo. Finally, as an open source developer, i love that Travis CI is free for all OSS repos. **What do you dislike about Travis CI?** Sometimes the service has outages, but i am not a customer of the paid product, only the free for open source projects. The build machines are also little bit slow. The CI is simple, but maybe too simple: you cannot see your working directory, cannot add new SDKs easily etc. **Recommendations to others considering Travis CI:** I would definitely recommend it. **What problems is Travis CI solving and how is that benefiting you?** If you are familiar with terminal environments this is the CI for you. ### 40. My OSS project was the highest-capacity user in the US, and I couldn't be happier **Rating:** 5.0/5.0 stars **Reviewed by:** Hamilton T. | Senior Director of Engineering and Research, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** April 09, 2016 **What do you like best about Travis CI?** * Incredibly fast - jobs are started nearly instantly * good limits for free tiers * very IT savvy and customer-centric support team - they reached out to us about hitting limits and understood our software limits that were triggering some issues **What do you dislike about Travis CI?** * website is occasionally slow or laggy, could be slimmed down * Programmatic APIs are not the quickest * Team is slow(ish) to respond on complex github issues (granted, I was on a free tier!) * No mechanisms for dynamic build matrix configuration, it must be done statically * * This is often called "touchstone" builds in other CI systems, and by executing initial sanity checks and then scheduling followup builds you can prevent unneeded resource consumption and get the max value out of your current limit tier **Recommendations to others considering Travis CI:** Just buy in, Travis is worth it. GitLab's runners are modeled after Travis jobs and are quite similar, but GitLab does not provide the same level of amazing support **What problems is Travis CI solving and how is that benefiting you?** Needed very rapid develop-iterate cycle to help convince OSS community members to devote their free time to our (quite complex) software stack that needed a *lot* of experts from different fields. We saw community interaction increase massively (4x) after we started using Travis-CI as domain experts were able to quickly propose a pull request and have Travis help them verify it without them needing to set up a 3-computer system just to run a benchmark and verify the output. ### 41. Great tool for improve software quality **Rating:** 4.5/5.0 stars **Reviewed by:** Nikolay G. | Software Engineer, Internet, Enterprise (> 1000 emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Travis CI?** Integration with github is great and allows to simply run tests on commits and monitor health of the project. Pull request checking is also a major, especially for a large open source project, because it simplifies pull request review process. Run tests on multiple configurations and multiple python versions is a great for library developers. Travis CI dashboard is pretty clean and informative. **What do you dislike about Travis CI?** It became harder to setup integration with a private repositories, if you are not owner of this repo, but this might be because of github restrictions. It might have a lack of flexibility for a large projects, but in my practice I never met this boundary. **Recommendations to others considering Travis CI:** It's pretty good and could solve most of the CI related problems **What problems is Travis CI solving and how is that benefiting you?** I use travis CI for running tests for my github projects. It's free for a small teams and perfectly fits for a python libraries developers ### 42. Travis is my goto for any open source CI projects **Rating:** 5.0/5.0 stars **Reviewed by:** Ben R. | Software Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** April 27, 2016 **What do you like best about Travis CI?** Simple and flexible setup. It supports a variety of technologies, and it's free. There are many examples out on the web and the Travis docs are detailed. **What do you dislike about Travis CI?** Travis doesn't scale well. I currently work on a project that uses 4 matrices that each run about 30 minutes. That in and of itself isn't the bad part. Travis limits resources for non-paying customers (as they should) and it often takes a long time for tests to start running if you have many contributors (10 or more). **Recommendations to others considering Travis CI:** If you're an open source project this is a great option to add CI to your project. **What problems is Travis CI solving and how is that benefiting you?** Before every pull request merge, Travis runs to ensure that our tests and some set of minimal functionality will work on the site. Without this, it'd be impossible to keep all the tests from breaking constantly. ### 43. Continious integration, deployment and test automation with Travis **Rating:** 4.5/5.0 stars **Reviewed by:** Alexander K. | Senior Software Developer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** March 17, 2016 **What do you like best about Travis CI?** The best of Travis CI is it's user-friendly GitHub integration. If you are using popular programming language - you will not get any problems. Moreover Travis CI provides huge capabilities for further customization. You can use default patterns to configure your build, tests and deployment or write it by your hands, because Travis CI provides Linux shell where you can do anything you want. Travis CI docs are also user frienly and easy to understand. Good integration with some services like Coveralls, Docker Hub. **What do you dislike about Travis CI?** You can use Travis CI only for Linux and Mac builds. If you need only windows - Travis CI is not your choise. If you are needed to use sudo - your build will start on low priority outdated infrastructure. That means longer build time and longer queues. Advanced configuration requires good knoledge in linux command line instruments, because there is no graphic interface for it. **Recommendations to others considering Travis CI:** I recomend to try it by yourself. Just open docs, find your programming language and enjoy! **What problems is Travis CI solving and how is that benefiting you?** I am using Travis CI to test my libraries, upload coverage to coveralls and deploy documentation to GitHub Pages. The main benifits are from GitHub integration. With Travis CI you no longer need to check build state for the different platfors of the pull requests by yourself, Travis will do it for you. After merge Travis CI will deploy documentation, binaries, make a tag, publish, or anything you want it to do automatically. ### 44. Excellent CI tool for open source projects **Rating:** 5.0/5.0 stars **Reviewed by:** Karl D. | Software Developer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Travis CI?** The absolute best thing with Travis CI is that it is free for open source projects. It is easy to connect your Github account and configure it to compile and run all your tests upon new commits. I think that Travis CI is a given choice if you are working with an open source project. **What do you dislike about Travis CI?** I personally wished that there were more configurations options to use. For example, one of Jenkins' strongest features is that you can configure it and personalise it with additional configurations or plugins. I wished that these options existed for Travis CI as well. Travis CI will look rather slim compared to Jenkins in certain aspects. **Recommendations to others considering Travis CI:** Give it a try if you are working on a open source project. **What problems is Travis CI solving and how is that benefiting you?** The benefits with Travis CI is that they host and manage everything. They solve ### 45. Very efficient and easy **Rating:** 5.0/5.0 stars **Reviewed by:** Gopalakrishnan V. | Lead - Product Management, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** May 18, 2016 **What do you like best about Travis CI?** It is very easy to integrate within your repository to automate the build and update process. Very straightforward processes and clear documentation make it helpful. **What do you dislike about Travis CI?** Pricing seems slightly arbitrary as it jumps from free open source to concurrent jobs. I think they need to think about what features they want to charge for and make it easier for their customers to move from one plan to another as they grow. **What problems is Travis CI solving and how is that benefiting you?** We used it primarily to run build scripts and keep the most current git branch updated on our hosted site. That way, the developers didn't have to handle the deployment duties and Travis was able to get the branch built and ready for QA on a regular basis. ### 46. One of the best CI servers in the market **Rating:** 5.0/5.0 stars **Reviewed by:** Tasdik R. | Network and Systems Administrator, Education Management, Mid-Market (51-1000 emp.) **Reviewed Date:** March 11, 2016 **What do you like best about Travis CI?** I am an open source developer so naturally I have a bias for Travis CI. I mostly use Travis CI for my open source projects. And I have never felt the need to shift to another CI server out there in the market. The documentation is good and if you ever need any help, the support team is always there to help you out. **What do you dislike about Travis CI?** My only complain would would be linux only builds. This is where Circle CI is essentially ahead. If you are building something cross platform, you will have to use something else along with it. They were telling about Windows support coming up in the later stages, but I don't see it anywhere soon. **Recommendations to others considering Travis CI:** I would Travis CI to everyone who wants to automate his build automation, continous integration. It's free for open source projects so I think it is a no brainer on what to choose **What problems is Travis CI solving and how is that benefiting you?** Mostly all things open source. I contribute as well as make a lot of my tools open source. As because of this I get a lot of PR's on github. And running tests is essential for merging them. ### 47. excellent ci **Rating:** 5.0/5.0 stars **Reviewed by:** Yasmany C. | DevOps Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** April 07, 2016 **What do you like best about Travis CI?** Is easy to configure and allows you to get really fast to the matrix of testing scenarios and version of your application or library. It enable almost all tools available now a day. Containerized testing methodology that ensure isolation of execution and results. It enhance and support open software development, helping thousands of projects. **What do you dislike about Travis CI?** It does not provide a tool to debug the container on execution. It should provide an ssh kinda like tool to interact with the testing container and reduce time on debugging tasks. **Recommendations to others considering Travis CI:** You will love the easiest of configuration and how quick you can get to your matrix of testing. It presents to your a great set of tools that will allow you to CI/CD and automate test in a few minutes. **What problems is Travis CI solving and how is that benefiting you?** CI private and open source projects. ### 48. Travis CL **Rating:** 5.0/5.0 stars **Reviewed by:** Kiarash T. | Small-Business (50 or fewer emp.) **Reviewed Date:** April 13, 2016 **What do you like best about Travis CI?** Really like the automatic tests, makes sure nobody pushes anything to the repository if it ends up breaking the repository. So you always wait for the green like from Travis ensuring you can push. **What do you dislike about Travis CI?** I don't have a lot of negative things about travis, I used it for one of my repositories but I do sometimes find it troubling which tests did it fail and why exactly. **Recommendations to others considering Travis CI:** It takes a little while to get used to, but it is a must have integration with your GitHub repositories if you need to make sure certain things to remain the same. **What problems is Travis CI solving and how is that benefiting you?** I'm in a non profit organization, ACM, and we use travis to make sure when we update our website with new events and workshops we don't break our repository. ### 49. Great tool for Continuous Integration **Rating:** 5.0/5.0 stars **Reviewed by:** Mathias F. | Senior Software Engineer, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** February 24, 2016 **What do you like best about Travis CI?** Before using Travis, I tried many other tools and even used TeamCity for a few months. I love how Travis is so simple and powerful at the same time. Each time I deploy anything, it's only writing a few lines to configure how Travis will test my application and everything is working right away from the first commit. **What do you dislike about Travis CI?** For some kinds of applications, it was a bit difficult to configure Travis. For Grails for example, I had to guess how to configure it because the documentation did not cover it. **Recommendations to others considering Travis CI:** Read the instructions for each framework and configure the notifications correctly. If you don't get notified, there is no use for Continuous Integration. **What problems is Travis CI solving and how is that benefiting you?** When working as a team with TDD, it's important to keep the tests passing at any time. Travis makes it very easy to check if that's the case. If it's not, it makes the person responsible know it by annoying him with awful red colored mails until he fixes it. ### 50. Automatic build with TRAVIS **Rating:** 4.5/5.0 stars **Reviewed by:** Andreas P. | Head of Web and Android Development, Higher Education, Mid-Market (51-1000 emp.) **Reviewed Date:** April 13, 2016 **What do you like best about Travis CI?** Easy to implement. Took me less than 10 minutes to get builds on every commit/pull request. This is very handy because that means I can teach my oc workers abot this product as well and we can work together to always make sure that our lint rules pass, that our tests work and that no tests fail. The travis build fails if there is an error and we get alerted right away. We can even check the messages before we merge a pull request. **What do you dislike about Travis CI?** The automatic deploy support was not as good as I'd hoped. I ran into some troubles deploying to heroku. **Recommendations to others considering Travis CI:** Do it. No drawbacks as far as I know. **What problems is Travis CI solving and how is that benefiting you?** Making the deployments more smooth, and not having to do it manually ## 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?section=pricing&secure%5Bexpires_at%5D=2026-05-15+01%3A34%3A15+-0500&secure%5Bsession_id%5D=ed6b5bd7-2692-4f89-b1d1-442728f9cb10&secure%5Btoken%5D=e8fdb408a9b16fcc529feebe7dcec010e8fb582bf58dd499b31c69560b476b66&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 (548 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)