Jenkins vs. Snap CI vs. Solano CI
|
|
|
|||||
Jenkins |
Snap CI |
Solano CI |
|||||
Favorites299
|
Favorites14
|
Favorites12
|
|||||
Hacker News, Reddit, Stack Overflow Stats |
|||||||
GitHub Stats |
No public GitHub repository stats available
|
No public GitHub repository stats available
|
|||||
Description |
What is Jenkins?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 Snap CI?Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.
|
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.
|
||||
Pros about this tool |
|
|
|
||||
Cons about this tool |
|
|
|
||||
Pricing |
|
|
|||||
Companies |
1456 Companies Using Jenkins
|
7 Companies Using Snap CI
|
12 Companies Using Solano CI
|
||||
Integrations |
Jenkins
Integrations
|
Snap CI
Integrations
|
Solano CI
Integrations
|
||||
|
What are some alternatives to Jenkins, Snap CI, and Solano CI?
|
|||||||
Latest News |
Jenkins is accepted to Google Summer Of Code 2018, j...
February 18, 2018
Security updates for Jenkins core
February 13, 2018
CloudBees + Codeship Means More is Coming to Jenkins
February 06, 2018
|
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
|
|||||
Reviews of Jenkins, Snap CI, and Solano CI
Great 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.
Better 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)
How developers use Jenkins vs Snap CI vs Solano CI
Pinterest uses Jenkins
Jenkins is our continuous integration system for packaging builds and running unit tests after each check in.
Kalibrr uses Jenkins
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.
PMoelA uses Jenkins
Is for continuous integration and monitoring of the app - the app is deployed for test through Jenkins - dashboard for monitoring of status on GitHub, App health etc.
Goyoboard uses Jenkins
Continuous integration that run all test and build scripts, we separate it into few build stages for multiple sub-modules.
RocketFuel uses Jenkins
Jenkins is used for running tests before and after merge, for deploying changes and for running periodic tasks, similarly to cron.
tiferrei uses Jenkins
More customisable continuous integration, very useful for Swift compiling and PR management.
softwareantelope uses Jenkins
Continuous integration with built-in testing so every release is safe and any errors are picked up immediately.
Vinceveve uses Jenkins
Automating build, running specs, blocking pull request, deploy on the Kubernetes, Jenkins does this all with ease.
JimmyLv uses Jenkins
CI/CD, Jenkins 2.0
- Groovy (Jenkinsfile.groovy: Pipeline as code)
- build slave (aws ec2)
- checkpoint stage
- build
- e2e
- deploy to dev
- deploy to sys
- e2e test
- deploy to uat
- shell scripts
ci.she2e.shdeploy.shpublish.shpublish-docs.sh
Clarabridge CX Social uses Jenkins
Used for continuous integration; e.g. running unit tests before deployment and of open GitHub Pull Requests.
Trusted Shops GmbH uses Jenkins
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.
nickdecooman uses Jenkins
Experience with overall Jenkins configuration, setting up agents and (multi-branch) continuous deployment pipelines through Jenkinsfiles.
AngeloR uses Jenkins
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.
Wirkn Inc. uses Jenkins
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.
testim-tests uses Jenkins
We automate our release cycle and use it to trigger our tests once a new code was pushed
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."
