What is CircleCI?
What is Solano CI?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Solano CI?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
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)
I use CircleCI as part of a cross platform mobile app to build and test the app as well as deploying .apk files to an s3 bucket.
Alongside CircleCI this repo also has a TravisCI setup for iOS. The CircleCI build has always been quicker and since moving from CircleCI v1 to CircleCI v2 it blows the TravisCI build out of the water. I'm really impressed with the performance gains from moving to v2. I'm pretty sure I could achieve similar results in Travis as well, but it was really easy to setup the Android CI build in Circle making use of Docker.
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!
After trying several CI systems, we stuck with CircleCI because of the inference engine in CircleCI 1.0 made setup a breeze. We were up and running quickly. Builds are reliable, nicely integrated into GitHub, and anytime we've had a question, the support team was there to help. The 2.0 system provides Docker support and far more customization and is still fairly easy to set up with helpful documentation.
CircleCI has become our CI of choice. The UI is really good and it has all the integrations we need. The 2.0 upgrade was not yet possible for one of our projects due to outdated gems, however, I have been able to get it working for a different one.
It help us with the automated build and test and also provide us with the build artifacts which we can use for the deployment also give use archive for each of our build, this things save us alot of time and cost
We use CircleCI to deploy to server. It is much easier than other websites like Travis especially for the free tier. It is especially useful for open source projects that need private access behind the scenes.
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.
"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."
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).
We originally used CircleCI as our self-contained build system for our internal node modules. It was very easy to set up and configure. Unfortunately we ended up stepping away from it to Jenkins and then CodePipeline due to better integration with our various applications.
We prefer CircleCI because we care about testing our apps. We found it is better to invest the time writing rSPEC tests to ensure we don't insert any regression bugs with new branches. It's also nice to have a fully-automated deployment process from GitHub to Heroku.
Used for CI/CD for all proofs of concept and personal projects, because of ease of use, GitHub integrations, and free tier.
Also used for example repos hosted in GitHub, paired with Dependabot, so that example repo dependencies are kept up to date.
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.
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.
CircleCI is used as continues integration system for shiro and all of its modules.
It automatically deploys the latest GitHub commit to https://shiro.host/.
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.
CircleCI will be used for deployment and continuous integration using a scripted configuration that deploys to Amazon EC2.
To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel