Travis CI vs. wercker vs. Solano CI
|
|
|
|||||||
|
|
|
|
|||||||
Hacker News, Reddit, Stack Overflow Stats |
|||||||||
GitHub Stats |
No public GitHub repository stats available
|
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 wercker?Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
|
What is Solano CI?Faster Continuous Integration and Deployment with patented auto-parallelization. See results 10 to 80x faster. 14-day free trial. No credit card required.
|
||||||
Want advice about which of these to choose?Ask the StackShare community! |
|||||||||
Pros |
|
|
|
||||||
Cons |
|
|
|
||||||
Pricing |
How much does Travis CI cost?
|
How much does wercker cost?
|
How much does Solano CI cost?
|
||||||
Companies |
What companies use Travis CI?
832 companies on StackShare use Travis CI
|
What companies use wercker?
58 companies on StackShare use wercker
|
What companies use Solano CI?
13 companies on StackShare use Solano CI
|
||||||
Integrations |
What tools integrate with Travis CI?
44 tools on StackShare integrate with Travis CI
|
What tools integrate with wercker?
6 tools on StackShare integrate with wercker
|
What tools integrate with Solano CI?
15 tools on StackShare integrate with Solano CI
|
||||||
What are some alternatives to Travis CI, wercker, and Solano CI?
|
|||||||||
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
|
Deprecating Older Solano CLI Versions
October 06, 2017
Announcing Custom Worker Volumes
August 10, 2017
Migrating from Snap CI to Solano CI
April 05, 2017
|
|||||||
Related Comparisons
Interest Over Time
Reviews of Travis CI, wercker, and Solano CI
-
sdhullBetter than the rest, since forever
February 17, 2016 19:30
Some of the stuff I've enjoyed the most about Solano:
- turnkey parallelism out of the box, with very little setup required (ie, it's fasstttt with almost no work)
- in all, when I set it up 2 years ago, I found it much easier to set up than the competitor service we were using at the time (and I've set up a couple competing services since then -- this is is still the easiest)
- sane defaults, project auto-detection, extensive configuration available (versions of everything)
- useful parsed results that are sortable & filterable (ie, you can filter just to show failed specs)
- github integration (commit hooks + badges on PRs)
- cached dependencies (for ruby, it's the bundle by default but you can add custom stuff like assets)
- infinitely customizable (I set up a project to run specs for a mobile app I'm building. maybe not impressive to some of you but as a rails developer, I thought it was cool)
Ease of Use Documentation Reliability Support -
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 -
keightyGreat team to work with
June 22, 2015 16:36
Solano is a great CI tool, and it has become an essential part of our build process. The suite builds in parallel, which makes test runs fast. The support team is super responsive and helpful.
Ease of Use Documentation Reliability Support
How developers use Travis CI vs wercker vs Solano CI
-
Airbnb uses Solano CI
"There are a ton of excellent strategies for speeding up Rails test suites—aggressive use of stubbing/test doubles, decoupling logic from models, avoiding loading Rails entirely—but given the size of our codebase and the velocity with which we’re moving, most of these weren’t immediately feasible. We needed a build system that would allow us to parallelize our test suite so that the real time taken to run the suite was manageable.
Our SRE team went through several different continuous integration solutions in the last year before settling on Solano.
Each of the previous systems had some issue: instability, memory consumption, poor DB management, poor parallelization, painful web UI, you name it. What Solano gives us is an on-premise solution with excellent native support for fanning out tests to multiple threads, running them in parallel, and then assembling the results. It has a great web UI, CLI support, and impressive performance. Since we started using it, our deploy workflow has grown noticeably faster, and the number of wails and anguished GIFs from frustrated engineers is at an all-time low."
-
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).
-
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.
-
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
-
-
-
