Great tool for TDD, CI and CD
January 23, 2017
Great tool for TDD, CI and CD
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Travis CI
We've been using Travis CI from day one. We believe continuous integration and continuous deployment are great ways to build a great product for our clients while keeping the quality standard high. Every feature we develop has its own set of tests, and if they fail in Travis CI, everyone's mission is to fix them as soon as possible so that we are back on track. As per the deployment process, we are releasing a new version of our API almost once a day. This is extremely easy if you have the assurance that Travis CI gives you.
- Smooth integration with our GitHub account.
- Test environment easy to configure.
- Quick and useful notifications when build fails.
- Integration with other repositories.
- Support for other languages.
- Software Quality is greatly influenced by Travis CI, as we detect problems very quickly with its help.
- Time to Market for a new product is reduced as your deployment process is less complicated.
- Release Train can be as rapid as once-per-day.
Jenkins is much more complicated to configure and start using. Although, one you have done that, it's extremely powerful and full of features. Maybe many more than Travis CI. As per TeamCity, I would never go back to using it. It's also complicated to configure but it is not worth the trouble. Codeship supports integration with GitHub, GitLab and BitBucket. I've only used it briefly, but it seems to be a nice tool.