Wir helfen Unternehmen seit 18 Jahren,
bessere Software zu finden
Was ist Buddy?
Erstelle, teste und implementiere Web-Projekte mit Code aus GitHub, GitLab oder Bitbucket über einen einzigen Sendevorgang ins Repository.
Wer verwendet Buddy?
Web- und Softwareentwickler, digitale Agenturen, Designer, technische Texter
Du bist nicht sicher, ob Buddy das Richtige ist?
Mit einer beliebten Alternative vergleichen
Buddy
Weitere gute Alternativen zu Buddy
Bewertungen über Buddy
In Betracht gezogene Alternativen:
Great tool fo CI/CD
Kommentare: This is a great choice for continuous integration and continuous delivery for small teams and developers.
Vorteile:
The Buddy interface is comfortable. Pipelines configuration is easy. You can customize pipelines in the UI or in YAML files.
Nachteile:
Occasionally, there are problems with the cache, and I must run the pipeline one more time with cache clearing.
In Betracht gezogene Alternativen:
Just try it, you will love it!
Kommentare: I have used many DevOps platforms in business ranging from small startups to massive global companies and Buddy is my personal favorite. It is simply a nice product to use and you have far more "oh awesome" moments then "$@!?$" moments then with any other tools.
Vorteile:
Buddy is elegant. It has the ability to do complicated things in simple intuitive ways. The combination of being able to hybrid YAML and GUI is a great example. You can use the intuitive GUI to quickly build out your pipelines and then bring it under source control with a couple of clicks. The GUI still works for read only making it easily accessible to less pipeline technical folks while also giving those maintaining the pipeline all the benefits of "as code".
Nachteile:
The dedicated number of workers and price per work is a shame in a cloud world. Would be neat if it was just based on compute hours etc. but maybe with some kind of fair usage policy for concurrency
This is a toy that you can use for a hobby project
Kommentare: Absolutely avoid. Spent last year trying to make it work and now the cost of keeping it alive is just too big so swapping as we speak. Last response from support I had... oh wait, I didn't have any.
Vorteile:
WHEN it works, it has a few good features. It allows you to a basic CI/CD for a small projects, that's about it.
Nachteile:
There's about 2h a day their support works, you have to wait for hours to get any response. And once you do 99% of those responses are "not our fault, try removing all projects, all integrations and try again". On the top of that anything more complex that "hello world" runs out of their apparent 2CPU 2GB deployment server. Want more resources? Wait for 24h until dev team has this 2h of work somewhere in India.
Very intuitive interface but very expensive
Kommentare: For me, Buddy should create a specific Plan for the people who wants ONLY the continus deployment functionnality without any complexity, or just decrease the Pro plan price, if it becomes €5 per month I will switch all my projects on it, or maybe €2 per project per month?
Vorteile:
Very intuitive UI/UX and the free account possibility
Nachteile:
The pricing is very very very expensive. Pro plan is about €29 / month, even my VPS does not cost this price 😅
In Betracht gezogene Alternativen:
One of the easiest ways to build and learn CI/CD
Kommentare: I have realized the easy to use CI pipeline I've created to save a lot of time deploying my app to a production environment. I was first exposed to CI/CD in general through my role as a Web Developer and used Buddy as my first pipeline builder. The experience was so enlightening that I'm now using it in my personal project to deliver updates to my application in a sophisticated manner. This allows me to spend more time code and strategizing versus the rudimentary manual process I'm used to.
Vorteile:
I like Buddy for the ease of use when you are a budding developer looking to learn CI/CD practices.
Nachteile:
If you're an entry to mid level developer, I feel there is an initial learning curve to learning CI/CD in general. The documentation is satisfactory but it would be improved if each section or sub-section had a "You should know this before reading" bit in the first part of the article. That way a self-taught learner can establish the connection between Buddy and the rest of their stack by understanding key elements that necessitate the use of Buddy or how they are best augmented by what Buddy can do.
