CircleCI vs. Buildkite
|
|
|||||
|
|
|
|||||
Hacker News, Reddit, Stack Overflow Stats |
||||||
GitHub Stats |
No public GitHub repository stats available
|
No public GitHub repository stats available
|
||||
Description |
What is CircleCI?CircleCI’s continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. CircleCI offers a modern software development platform that lets teams ramp
|
What is Buildkite?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.
|
||||
Want advice about which of these to choose?Ask the StackShare community! |
||||||
Pros |
|
|
||||
Cons |
|
|
||||
Pricing |
How much does CircleCI cost?
|
How much does Buildkite cost?
|
||||
Companies |
What companies use CircleCI?
1013 companies on StackShare use CircleCI
|
What companies use Buildkite?
46 companies on StackShare use Buildkite
|
||||
Integrations |
What tools integrate with CircleCI?
54 tools on StackShare integrate with CircleCI
|
What tools integrate with Buildkite?
14 tools on StackShare integrate with Buildkite
|
||||
What are some alternatives to CircleCI and Buildkite?
|
||||||
Latest News |
Automate open source security tracking with the Whit...
February 15, 2019
How to output JUnit tests through CircleCI 2.0 for e...
February 14, 2019
Build a Clojure web app using Duct
February 12, 2019
|
|||||
Related Comparisons
Interest Over Time
Reviews of CircleCI and Buildkite
-
lewnelsonEasy to use and super quick
February 15, 2018 11:36
I use CircleCI as part of a cross platform mobile app to build and test the app as well as deploying .apk files to an s3 bucket.
Alongside CircleCI this repo also has a TravisCI setup for iOS. The CircleCI build has always been quicker and since moving from CircleCI v1 to CircleCI v2 it blows the TravisCI build out of the water. I'm really impressed with the performance gains from moving to v2. I'm pretty sure I could achieve similar results in Travis as well, but it was really easy to setup the Android CI build in Circle making use of Docker.
Ease of Use Documentation Reliability Support -
regentgalEasy to setup, great flexibility, awesome support
January 21, 2018 21:02
After trying several CI systems, we stuck with CircleCI because of the inference engine in CircleCI 1.0 made setup a breeze. We were up and running quickly. Builds are reliable, nicely integrated into GitHub, and anytime we've had a question, the support team was there to help. The 2.0 system provides Docker support and far more customization and is still fairly easy to set up with helpful documentation.
Ease of Use Documentation Reliability Support -
shannonwellsGood availability, stays current, great ease of use
February 07, 2018 11:04
CircleCI has become our CI of choice. The UI is really good and it has all the integrations we need. The 2.0 upgrade was not yet possible for one of our projects due to outdated gems, however, I have been able to get it working for a different one.
Ease of Use Documentation Reliability Support -
ryuzaki01Easy to use
April 08, 2018 18:22
It help us with the automated build and test and also provide us with the build artifacts which we can use for the deployment also give use archive for each of our build, this things save us alot of time and cost
Ease of Use Documentation Reliability Support -
nahtnamEasy to Use CI/CD
April 02, 2018 14:34
We use CircleCI to deploy to server. It is much easier than other websites like Travis especially for the free tier. It is especially useful for open source projects that need private access behind the scenes.
Ease of Use Documentation Reliability Support
How developers use CircleCI vs Buildkite
-
toolmantim uses Buildkite
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.
-
AngeloR uses CircleCI
We originally used CircleCI as our self-contained build system for our internal node modules. It was very easy to set up and configure. Unfortunately we ended up stepping away from it to Jenkins and then CodePipeline due to better integration with our various applications.
-
jflynn33 uses CircleCI
We prefer CircleCI because we care about testing our apps. We found it is better to invest the time writing rSPEC tests to ensure we don't insert any regression bugs with new branches. It's also nice to have a fully-automated deployment process from GitHub to Heroku.
-
welkie uses CircleCI
Used for CI/CD for all proofs of concept and personal projects, because of ease of use, GitHub integrations, and free tier.
Also used for example repos hosted in GitHub, paired with Dependabot, so that example repo dependencies are kept up to date.
-
Marc3842h uses CircleCI
CircleCI is used as continues integration system for shiro and all of its modules.
It automatically deploys the latest GitHub commit to https://shiro.host/.
-
jasonmjohnson uses CircleCI
CircleCI will be used for deployment and continuous integration using a scripted configuration that deploys to Amazon EC2.