Need advice about which tool to choose?Ask the StackShare community!
Semaphore vs wercker: What are the differences?
Semaphore: The continuous integration and delivery platform powering the world’s best engineering teams. Semaphore is the fastest continuous integration and delivery (CI/CD) platform on the market, powering the world’s best engineering teams; wercker: Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Semaphore and wercker can be primarily classified as "Continuous Integration" tools.
Some of the features offered by Semaphore are:
- Docker, Kubernetes, iOS support & 100+ preinstalled Tools
- Customizable Continuous Delivery Pipelines
- Customizable Stages, Parallel Execution and Control Flow Switches
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.
"Easy setup" is the top reason why over 19 developers like Semaphore, while over 34 developers mention "Automatic Deployments" as the leading cause for choosing wercker.
FashionUnited, Hazeorid, and Wantedly are some of the popular companies that use wercker, whereas Semaphore is used by Pipefy, Weroom, and CrowdFlower. wercker has a broader approval, being mentioned in 40 company stacks & 23 developers stacks; compared to Semaphore, which is listed in 40 company stacks and 17 developer stacks.
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 Semaphore
- Easy setup20
- Fast builds15
- Free for private github repos14
- Great customer support8
- Free for open source6
- Organizations ready5
- Slack integration4
- SSH debug access2
- GitHub Integration2
- Easy to use1
- Continuous Deployment1
- Pipeline builder GUI1
- BitBucket integration1
- Docker support1
- Simple UI1
- Parallelism1
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
Sign up to add or upvote prosMake informed product decisions
What is Semaphore?
What is wercker?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Semaphore?
What tools integrate with wercker?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+44