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.
What is Semaphore?
What is wercker?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Semaphore?
What are the cons of using wercker?
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
When it comes to continuous Integration services, the choice is hard. There are several solutions available and it looks like the dev scene is very split. We've read and reviewed several solutions and we ended up making the choice between Codeship and Semaphore . Although Semaphore is used by slightly more developers, we've experienced a faster and easy flow using Codeship. Both do integrate Slack and GitHub very well, so this is not a point to set them apart. Both have a complex pricing system that is not that easy to calculate and predict. However, out in the wild, we found Codeship to have a better price point at heavy use.
The Bitbucket integration with branch whitelists allows you to conserve your 100 builds this month.
CI and Deploy (Ionic Viewer and Heroku)
master -> Deploy develop -> CI