Travis CI Reviews & Product Details

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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). Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

The automatic deploy support was not as good as I'd hoped. I ran into some troubles deploying to heroku. Review collected by and hosted on G2.com.