Need advice about which tool to choose?Ask the StackShare community!
Solano CI vs wercker: What are the differences?
Developers describe Solano CI as "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. On the other hand, wercker is detailed as "Build, test, and deploy container-native applications". Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Solano CI and wercker belong to "Continuous Integration" category of the tech stack.
Some of the features offered by Solano CI are:
- 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
- Compatible with most developer environments: seamlessly supports popular languages such as Java, C/C++, Python, Ruby, JavaScript, Scala, PHP and Go
On the other hand, wercker provides the following key features:
- Pipelines - Wercker's Pipelines enable developers to fully automate builds, tests and deployments with Docker as a first class citizen.
- Workflows - With Workflows: a collection of pipelines can be chained and triggered to achieve complex automation goals.
- Steps Store - A step is a self contained best practice for accomplishing a specific automation task. Build your own or help yourself to our community based store.
"Uber-fast highly customizable parallel builds" is the top reason why over 9 developers like Solano CI, while over 34 developers mention "Automatic Deployments" as the leading cause for choosing wercker.
We migrated all our CI/CD pipelines to CircleCI back in 2017 and are particularly happy about it since!
Our top loved feature is unlimited parallelism. We can run as many builds concurrently as we want.
We also use orbs, pipeline parameters, reusable commands, build cache, test insights.
For some of the heavier repos, we use a larger resource class and mount RAMdisk to a file system to speed up builds.
Pros of Solano CI
- Uber-fast highly customizable parallel builds10
- Awesome support and easy to integrate!7
- Github integration and automatic branch tracking7
- Integration with AWS Code Pipeline3
- Powerful and flexible with super helpful service2
Pros of wercker
- Automatic Deployments35
- Free33
- Easy config via yaml25
- Awesome UI23
- Github integration23
- Continuous Deployment22
- Supports both Github and Bitbucket16
- Easy to setup14
- Reliable12
- Bitbucket Integration11
- Community-driven components (boxes and steps)4
- Fast builds4
- Easy to get started4
- Docker based4
- Easy UI3
- Flexible configuration via YAML3
- Multi-target deploys2
- Trigger by branch name1
- Great UI, free and an active Slack channel :)1
- Docker support1
- Multiple configurable build steps1
