レビュー募集中！Buddyを紹介・競合製品の評判をユーザーレビュー・口コミで紹介

What do you dislike?

We noticed that a few options from the UI aren't available through the yml configuration, not sure if this is still the case but we haven't really used those features anyway.

It is a bit pricy but we work for customers so they get to pay for our usage.

Last time I tried there was no docker compose support, however having a quick look at the docs there seems to be some progress in this?

What do you like best?

The best part about Buddy is that its is incredibly easy to pick up on. In no time you have a complete pipeline build in the easy to use UI. Afterwards (if you want to) you can export it to a yml file and put it in your source control. This way its easy to first setup your pipeline but still have the definition in your source control!

You create those pipelines by chaining actions, luckily there are a lot of actions available for almost every situation imaginable.

What do you dislike?

For startups, they can reduce the price because they are more prone to pipeline failures and need more focus on pipelines so when they grow, their pipelines grow.

What do you like best?

Buddy's GUI is really awesome and to create pipeline's using Buddy is really really simple. For a beginner who doesnt understand CICD much, start using Buddy and you will get to know everything related to CICD in a day. Buddy is also constantly improving and new features everyday.

What do you dislike?

Limited Open Source support (only 5 repos) so I have decommissioned this on most of my GitHub repos now in favour of other CI systems like GitHub Actions, Travis CI and Azure DevOps which are my top 3 (in that order, I still use a lot of other CI systems too, see https://github.com/harisekhon for a tonne of them).

The Yaml is a bit ugly with capitalized strings and too many explicit options from the generated default template.

Lots of options do not appear in the yaml to revision control, which would be ideal.

It's own quirks, where builds may get cancelled or fail for random reasons that aren't my code, eg. upstream apt repos are temporarily unavailable (unfortunately most CI systems don't detect and retry this properly so you must do some retries yourself).

Badge could be nicer looking, like GitHub Actions, Azure DevOps, Circle CI, Semaphore CI or the shields.io badges (shields.io supports tonnes of CI systems but not Buddy unfortunately, otherwise I would have replaced the "buddy.works" badge in my README.md with a nicer constructed one with flexible text, formatting & icon from shields.io)

What do you like best?

The UI looks ok, has pages to configure things (should really all be in yaml though for revision control), UI design is better than some other CI systems I've used

What do you dislike?

Lack of community - can make it tricky to troubleshoot specific issues at times, but the documentation mostly makes up for this (granted documentation can feel a little light at times)

What do you like best?

Simplicity, availability of common procedures, incredible support, great UI