Review on Travis CI by Matt Kim

I like that it integrates well into GitHub repos - as soon as you commit something new (ie after pushing) your tests run again automatically. It's not always obvious what needs running but once set up correctly there are no problems using this service. When our build runs for longer than expected we find ourselves having to wait until next day before seeing any results! This could be because other builds have been triggered during the night or even when my team has gone home so they don't see them either. If you're looking at integrating some automated unit/integration tests then travis will do exactly that without too much hassle. We use travis internally within our own project which means all changes go through the pull request process first here - if someone commits anything directly from github onto master branch it doesn't get tested unless requested via PR. I like that it is easy to use and has lots of integrations for different languages and frameworks. It also provides a lot of flexibility when running tests. The UI could be cleaner, but overall it's a pretty good tool. We've been using it for almost two years now and haven't had any issues. We're able to run our tests in multiple environments (e.g., local, staging, production), which helps us get feedback faster.