Jenkins vs Solano CI: What are the differences?
What is Jenkins? An extendable open source continuous integration server. In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
What is 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.
Jenkins and Solano CI can be categorized as "Continuous Integration" tools.
Some of the features offered by Jenkins are:
- Easy installation
- Easy configuration
- Change set support
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
"Hosted internally" is the primary reason why developers consider Jenkins over the competitors, whereas "Uber-fast highly customizable parallel builds" was stated as the key factor in picking Solano CI.
Jenkins is an open source tool with 13.3K GitHub stars and 5.48K GitHub forks. Here's a link to Jenkins's open source repository on GitHub.
What is Jenkins?
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 add, upvote and see more consMake informed product decisions
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."
All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.
Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.
- Continuous Deploy
- Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
- Staging and production stages: Build and rollback quicly with Ansistrano playbook
- Sending messages of job results to Chatwork.
Currently serves as the location that our QA team builds various automated testing jobs.
At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.
We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.