Buildkite vs Concourse: What are the differences?
What is Buildkite? Fast, secure and scalable CI/CD for all your software projects. CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.
What is Concourse? 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.
Buildkite and Concourse belong to "Continuous Integration" category of the tech stack.
"Great customer support" is the top reason why over 17 developers like Buildkite, while over 8 developers mention "Real pipelines" as the leading cause for choosing Concourse.
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.
According to the StackShare community, Buildkite has a broader approval, being mentioned in 37 company stacks & 7 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.
What is Buildkite?
What is Concourse?
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 Buildkite?
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
I use Buildkite because it's the only CI system I've found that strikes a reasonable balance between flexibility and usability. You can accomplish pretty much any standard CI task out of the box with a simple, easy to understand interface and sane defaults, while the hooks and pipeline systems offer enough configurability to rival Jenkins - but without the misery that using Jenkins is certain to entail.
I use Buildkite because it balances enormous flexibility with easy out of the box configuration. We use it for everything from automating builds (which involves running huge test suites where the parallel builds feature is invaluable) to doing nightly batch jobs for our production environment. Super flexible, amazing tool
Buildkite provides testing of the Rails application via a Docker container with Docker Compose. The Buildkite Agent runs on a small Digital Ocean droplet, runs the integration and model tests, and marks the GitHub commit for Heroku to perform their auto-deployments once the build is green.