Travis CI vs. Shippable vs. Testling
|
|
|
|||||||
|
|
|
|
|||||||
Hacker News, Reddit, Stack Overflow Stats |
|||||||||
GitHub Stats |
No public GitHub repository stats available
|
No public GitHub repository stats available
|
|||||||
Description |
What is Travis CI?Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
|
What is Shippable?Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.
|
What is Testling?Sign in with your browserling account. free for open source. No sign-up required. Just configure a github webhook.
|
||||||
Want advice about which of these to choose?Ask the StackShare community! |
|||||||||
Pros |
|
|
|
||||||
Cons |
|
|
|
||||||
Pricing |
How much does Travis CI cost?
|
How much does Shippable cost?
|
How much does Testling cost?
|
||||||
Companies |
What companies use Travis CI?
851 companies on StackShare use Travis CI
|
What companies use Shippable?
26 companies on StackShare use Shippable
|
What companies use Testling?
1 companies on StackShare use Testling
|
||||||
Integrations |
What tools integrate with Travis CI?
44 tools on StackShare integrate with Travis CI
|
What tools integrate with Shippable?
7 tools on StackShare integrate with Shippable
|
No integrations listed yet
|
||||||
What are some alternatives to Travis CI, Shippable, and Testling?
|
|||||||||
Latest News |
Integrate API tests with Postman, Newman, and Travis CI
August 22, 2017
Running Dusk tests on Travis CI and CircleCI
March 30, 2017
|
Joyent + Shippable Fireside Chat
March 15, 2017
|
|||||||
Related Comparisons
Interest Over Time
Reviews of Travis CI, Shippable, and Testling
-
tschellenbachPerhaps 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!
Ease of Use Documentation Reliability Support
How developers use Travis CI vs Shippable vs Testling
-
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
