Why we use Travis CI
August 29, 2017
Why we use Travis CI
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Travis CI
We use Travis CI for both our main app build and all the UI assets. It's set up to run on every commit, and a failed build will stop any merges to master.
Pros
- Simple to set up.
- Good documentation.
- Clean interface.
- Good level of customization.
Cons
- Speed.
- Job scheduling.
- Integrations.
- Saves time.
- Software stability, visibility.
- History.
Similar features. [Travis CI has a] Simpler interface and setup.
Comments
Please log in to join the conversation