Need advice about which tool to choose?Ask the StackShare community!
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.
Pros of Buddy
- Easy setup55
- Docker53
- Integrations49
- Continuous Integration49
- Beautiful dashboard45
- Git hosting44
- Free43
- Unlimited pipelines41
- Backup39
- Monitoring39
- Great UX36
- On-Premises32
- Awesome support31
- AWS Integrations6
- Great UI4
- Slack integration3
- Continuous deployment3
- Simple deployments3
- Hosted internally (Enterprise)3
- Bitbucket integration3
- Fast execution2
- Node.js support2
- Amazing + free2
- Azure integration2
- Github integration2
- UI and YML configuration2
- Shopify integration1
- Support for build pipelines1
- Docker support1
- Gitlab integration1
- Android support1
- Pushover integration1
- DigitalOcean integration1
- UpCloud integration1
- New Relic integration0
- Rollbar integration0
- Sentry integration0
- Loggly integration0
- Datadog integration0
- Bugsnag integration0
- Honeybadger integration0
- Telegram integration0
- HipChat integration0
- Discord integration0
- Pushbulet integration0
- Rackspace integration0
- Slack Integration0
- Google Cloud integration0
- Heroku integration0
- Kubernetes support0
- AWS integration0
Pros of CircleCI
- Github integration223
- Easy setup175
- Fast builds151
- Competitively priced94
- Slack integration72
- Docker support54
- Awesome UI44
- Great customer support33
- Ios support18
- Hipchat integration14
- SSH debug access12
- Free for Open Source11
- Bitbucket integration5
- Mobile support5
- AWS CodeDeploy integration4
- Nodejs support4
- Great support3
- YAML configuration3
- Free for Github private repo3
- Clojure2
- Simple, clean UI2
- Clojurescript2
- OSX support2
- Continuous Deployment2
- Android support1
- Autoscaling1
- Fair pricing1
- All inclusive testing1
- Helpful documentation1
- Japanese in rspec comment appears OK1
- Favorite1
- Build PR Branch Only1
- Really easy to use1
- Unstable1
- So circular1
- Easy setup, easy to understand, fast and reliable1
- Parallel builds for slow test suites1
- Easy setup. 2.0 is fast!1
- Parallelism1
- Extremely configurable1
- Easy to deploy to private servers1
- Works1
Sign up to add or upvote prosMake informed product decisions
Cons of Buddy
- Deleted account after 1 month of not pushing code1
Cons of CircleCI
- Unstable9
- Scammy pricing structure6
- Aggressive Github permissions0
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!
What companies use Buddy?
What companies use CircleCI?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with CircleCI?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7
+32
+5
+13
+22
+34
+39
+30