Concourse vs Semaphore: What are the differences?
Developers describe Concourse as "Pipeline-based CI system written in Go". Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control. On the other hand, Semaphore is detailed as "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.
Concourse and Semaphore can be categorized as "Continuous Integration" tools.
"Real pipelines" is the top reason why over 8 developers like Concourse, while over 19 developers mention "Easy setup" as the leading cause for choosing Semaphore.
Concourse is an open source tool with 3.99K GitHub stars and 482 GitHub forks. Here's a link to Concourse's open source repository on GitHub.
GrowthHackers, CrowdFlower, and Lost My Name are some of the popular companies that use Semaphore, whereas Concourse is used by DigitalOcean, Starbucks, and HelloFresh. Semaphore has a broader approval, being mentioned in 40 company stacks & 17 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.
What is Concourse?
What is Semaphore?
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?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Concourse?
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