The best hosted CI service available, IMHO
Overall Satisfaction with Travis CI
We use Travis CI for the automation of builds of all pull requests so we can be sure all tests from our test suit are passing, before we start code review.
Continuous integration of our projects, testing and automatically deploying into production upon successful merge of pull requests onto our master branches.
Pros
- I love the ease of use, the UI is very simple and well thought out, and it is still powerful enough.
- It integrates with Slack and keeps us informed of all build's status.
- It is easy to integrate with Heroku for deployment once builds have passed all tests.
Cons
- I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source.
- There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration.
- It saves you in infrastructure and setup costs, since running a server and installing and maintaining Jenkins can be a hassle.
There are a few other options out there, CircleCI, Codeship and Wrecker would be a few good ones I can also recommend, each one has its particularity but I believe Travis has the best interface and flexibility of all of them.
I'd recommend trying them all and seeing which one best fits your bill, since featureset and pricing is completely different between all of them.
I'd recommend trying them all and seeing which one best fits your bill, since featureset and pricing is completely different between all of them.
Comments
Please log in to join the conversation