Travis CI Reviews & Product Details

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

I have no complaints right now. So far it has been very straight forward and easy to use. Review collected by and hosted on G2.com.

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

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

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

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

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

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

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

I think that Travis is a bit difficult for new users and developers, especially configuring it for the first time. Review collected by and hosted on G2.com.

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

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

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

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

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

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

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

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

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

Over the many years I have been using Travis, I have not experienced anything i dislike. Review collected by and hosted on G2.com.