Travis CI Reviews & Product Details

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

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

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

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

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

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

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

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

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

.travis.yaml file little bit confusing, rest every thing works great Review collected by and hosted on G2.com.

I love the ease of use, the UI is very simple and well thought out, and it is still powerful enough. Review collected by and hosted on G2.com.

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

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

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

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

Since I'm not an advanced user I didn't notice any disadvantages yet. Review collected by and hosted on G2.com.

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

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

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

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