Buddy vs CircleCI: What are the differences?
What is Buddy? Build, test and deploy on push in seconds. Git platform for web and software developers with Docker-based tools for Continuous Integration and Deployment.
What is CircleCI? Automate your development process quickly, safely, and at scale. Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
Buddy can be classified as a tool in the "Continuous Deployment" category, while CircleCI is grouped under "Continuous Integration".
Some of the features offered by Buddy are:
- Automatic deployments on push to branch
- Docker-based builds and tests
- 10-minute setup of complete environment
On the other hand, CircleCI provides the following key features:
- Language-Inclusive Support
- Custom Environments
- Flexible Resource Allocation
"Docker" is the primary reason why developers consider Buddy over the competitors, whereas "Github integration" was stated as the key factor in picking CircleCI.
Instacart, Lyft, and StackShare are some of the popular companies that use CircleCI, whereas Buddy is used by Docplanner, Buddy, and Ambar. CircleCI has a broader approval, being mentioned in 925 company stacks & 372 developers stacks; compared to Buddy, which is listed in 20 company stacks and 14 developer stacks.
My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the
.coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the
.coverage file from my docker container and get the coverage report with #Codecov.
Buddy is one of the most easy-to-use tools for CI I ever met. When I needed to set up the pipeline I was really impressed with how easy it is to create it with Buddy with only a few moments. It's literally like: 1. Add repo 2. Click - Click - Click 3. You're done and your app is on prod :D The top feature that I've found is a simple integration with different notification channels - not only Slack (which is the one by default), but Telegram and Discord. The support is also neat - guys respond pretty quickly on even a small issue.
We picked up Buddy initially because it allowed us to structure and scale our usage as we grew. It also has some of the best integrations that we've seen (and that we used to script manually). We use it to deploy our cloud stack as well as package our on-premise software.
It's pretty versatile, and compared to the other tools pricing is much more sensible.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Buddy?
What is CircleCI?
Need advice about which tool to choose?Ask the StackShare community!
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