Perhaps the best CI tool
January 12, 2018 15:14
In the past we used to run Jenkins. The build server always had weird issues and was a pain to maintain. Travis is a great solution for CI. Their Debug build features makes it trivial to figure out why your build broke. The integration with Github is also very slick. One thing they could improve is the documentation on the .travis.yaml format. All in all, great company and very responsive supports. Over here at getstream.io we're a fan. Keep up the good work guys!
datapile uses Travis CI
Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.
It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).
giovannicandido uses Shippable
Very cheap and good quality integration service. Use docker as the underline infrastructure and is ready to deploy on many places like cloud foundry.
Its a build and reporter tool, continuous building the application
cuu508 uses Travis CI
While we usually run tests before commits, Travis goes further and tests with different Python versions and different database backends. It works great, and, best of all, it is free for open source projects.
Packet uses Shippable
Shippable allows us to run our testing framework on the same exact images that we run our stack in. This helps us avoid any issues with the testing framework being different than the production framework.
ruleant uses Travis CI
Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.
scrthq uses Travis CI
Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.
skarfacegc uses Travis CI
To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel