DotCi vs Solano CI: What are the differences?
DotCi: Jenkins plugin with GitHub and Docker integration. DotCi is a Jenkins plugin created by Groupon that makes job management easy with built-in GitHub integration, push-button job creation, and YAML powered build configuration and customization. It comes prepackaged with Docker support as well, which means bootstrapping a new build environment from scratch can take as little as 15 minutes. DotCi has been a critical tool for Groupon internally for managing build and release pipelines for the wide variety of technologies in their SOA landscape; Solano CI: Massively Scalable Continuous Integration and Deployment. Faster Continuous Integration and Deployment with patented auto-parallelization. See results 10 to 80x faster. 14-day free trial. No credit card required.
DotCi and Solano CI belong to "Continuous Integration" category of the tech stack.
Some of the features offered by DotCi are:
- Deep Integration with Source Control – for us that’s Github Enterprise
- Integration with Github webhooks
- Feedback sent to the committer or pusher via Email, Hipchat, Campfire, etc.
On the other hand, Solano CI provides the following key features:
- Parallel performance: safe parallel execution and dynamic task distribution finish builds up to 80x faster, automatically
- Painless, revision-controlled setup: fast self-service setup for new projects and branches, compact YAML configuration file that lives in the code repository
DotCi is an open source tool with 505 GitHub stars and 65 GitHub forks. Here's a link to DotCi's open source repository on GitHub.
What is DotCi?
What is Solano CI?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose DotCi?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using DotCi?
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)
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."