Buddy

Avantages

Facilité d'integration et de mise en place des pipeline de développement

Inconvénients

Pas grand chose, tout est bien détaillé, l'information est facile à trouver et dès que j'ai eu a contacter le support j'ai de suite été pris en charge.

Avantages

Buddy has the most convenient CI/CD and deployment functionalities. It's web-UI based work flow builder really stands out and helps beginner mobile devs to easily use continuous integration.

Inconvénients

Buddy's Pro plan doesn't really suffice for memory-hungry builds. Especially in android builds, I felt it's 3GB Ram for Pro plan isn't really close to what we need. Builds would usually fail due to memory issues, no matter how optimized the pipeline is

Alternatives envisagées 

Pourquoi choisir Buddy 

Avantages

I like Buddy for the ease of use when you are a budding developer looking to learn CI/CD practices.

Inconvénients

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.

Alternatives envisagées 

Pourquoi passer à Buddy

Avantages

* very easy to use
* new pipeline config is very simple
* multiple integrations
* on-premise plan
* options for pipelines discribed in yaml files or we can just click it one after another
* after registration its ready to work

Inconvénients

* complicated build are failing randomly (with multiple additional serwices) without logs - cannot investigate why. It occurs as on machine on 20G memory as also on 60G (guys are working on that)
* no integrations for output parsing (ex. junit is not parsed) only raw output
* limit of 4 additional services (ex. mysql) per pipeline action (I've already reached the limit and I need add some more services in near future)
* if using yaml config, its extremely easy to unintentionaly break pipeline for example having conflicts with merge on feature branch. Would be great if we could have an option for securing pipelines to read only from concrete branches (for ex. master and pipeline-dev),

Alternatives envisagées 

Avantages

The feature of defining actions and customize the actions based on the requirement. Switching on and off of the actions of a pipeline. When error occurred, correcting the issues and continue to run the pipeline.Parameter action and custom actions help to achieve what we want. Integration with third party tools like ACR, Synk- etc

Inconvénients

Selecting only one code repo for a project.

Avantages

The UX is so simple yet so powerful that anyone can create pipelines. Even our non-technical users understands the software and create pipelines to automate their needs from the code.

Inconvénients

The cap of concurrent runs is set to 4 on self-hosted. Even though the wait time is pretty low, it's still annoying when we deploy large amount of microservices.

Alternatives envisagées 

Pourquoi choisir Buddy 

Logiciel antérieur 

Pourquoi passer à Buddy

Avantages

- Very regular software updates, adding great new features all of the time
- Decent UI that allows us to do everything we need. YAML configuration available to those who don't want it
- Sensibly priced, self hosted option for those who want to keep it in-house
- Good integration with all of the tools we use and more

Inconvénients

- We have to manually renew our LetsEncrypt SSL through the CLI tool on the server
- Hardware requirements can be a little high if using Docker, but that's more of a Docker problem than Buddy

Alternatives envisagées 

Pourquoi choisir Buddy 

Avantages

- The filesystem access to debug builds and their artifacts
- The Dockerized containers for each action that share the filesystem
- The many ready to go actions that can be added to any pipeline
- The ability to have multiple pipelines running on a given project
- The ability to tag and organize repositories into folders

Inconvénients

- Requires a lot of memory for the self-hosted variant
- Inability to use slashes to group repositories under namespaces

Alternatives envisagées 

Pourquoi choisir Buddy 

Logiciel antérieur 

Pourquoi passer à Buddy

Avantages

We used DeployBot for the longest time but we just had so many inexplicable issues and frustratingly timed downtime along with slow response times.

Buddy has wiped the floor on all of these points. It takes a much more user focussed approach to deployment, giving you all the bits and pieces needed to construct a deployment/build system exactly how you need it. The way DB dictated a build system to us previously worked OK for us, but with Buddy you can achieve the same approach and so much more (or less if needed) just by virtue of it giving you complete control over every step. If you wanted to you could use it for other kinds of automation based on repos, for example we have a repo used for running checks on a live Magento database where data issues are not entirely uncommon — this pipeline runs checks there and notifies us if it finds something wrong.

Love Buddy, and we'll never be looking back.

Inconvénients

There are some minor edge case features I'd like to see, it doesn't tick every single possible box, but this is really so minor as whatever I'm referring to can be achieved somehow with thought.

Avantages

The integrations is by far the best feature of Buddy. it connects you with literally everything, Amazon, Google, Github, Slack, etc, etc, etc On top of that it allows you to run literally anything in their cloud.

Inconvénients

Not so much about the pricing structure, I'm paying $200 and it seems that I could get more

Alternatives envisagées 

Pourquoi choisir Buddy 

Logiciel antérieur 

Pourquoi passer à Buddy

Avantages

Really customer focused, good and fast support, easy to use and its always improving fast with new features. It just wotks :)

Inconvénients

It can be expensive if you need a lot of parallel jobs running. The support with the devs is not 24/7.

Alternatives envisagées 

Pourquoi passer à Buddy

Avantages

It's easy to use and have a nice interface

Inconvénients

I don't find any drawbacks for the time I used Buddy

Avantages

Ease of setup and use is key to any service. Every other service that I have used pales in comparison in this aspect

Inconvénients

Shared variable management can sometimes be tricky, especially when you have multiple pipelines.

Avantages

Its simplicity in setting the whole environment

Inconvénients

Nothing in particular, maybe the cost.

Avantages

As the account owner, with no direct hands on development, I appreciated the costs were well within reason.

Inconvénients

There are no features missing that I can see but I'm not the developer.

Avantages

It is very easy to get started with, intuitive. No real need to familiarize yourself with how the tooling works. We could quickly get pipelines up and running to test with and didn't need to spend much tweaking and fixing the build process. Our first intuition on how we should set it up was spot on. We could very quickly move from the initial test to using it in production.

Because of the simple look and feel of the product it was very easy to get the whole company on board, in a company that wasn't used to using build systems. Getting people familiar with the product for day to day use was very easy to do.

The initial set-up of the on-premise variant was very straight forward because they use docker. We ran a couple of commands and had it up and running in no time. Figuring out back-ups took a little more time but the customer service was great and they have updated the docs since.

Inconvénients

The only con I can come up with is the price. We need to use the on-premise/enterprise version and that one is quite expensive to start with and has a hefty mark-up when you pass one of the pricing stages. The price doubles when you go from 10 to 20 or 20 to 40 users which hurts a little when you are adding your 11th or 21th person to the team.

Avantages

Buddy is really easy to set up and start using as a CI, CD or DevOps tool. I've tried other tools in the past to help on CD processes but I always had a hard time to get somewhere. With buddy I created the first pipeline in minutes and it helped me a lot, since I was the only one who was deploying applications in the company.

Inconvénients

I love buddy :)
I don't remember any cons.

Avantages

Buddy is fast, it's easy, it's advanced. Buddy enables us to deploy without lots of hassle. We work with git-flow and as soon as we push a release, Buddy is ready to deploy it. We really love the advanced deployment features

Inconvénients

Buddy might be a bit overwhelming at first, after you learn the terms, where to setup a project, it will all be a walk in the park

Avantages

Flexibility. We use it to deploy anything from web apps with Vue.js, server-side applications with Laravel, WordPress and Node without any issues.

Inconvénients

Lack of documentation to set up automated tests. I'd like to run unit tests with Jest, so it would be great if there was clear examples on how to do so and fail a deploy on failed tests.

Avantages

The obvious positives for us about Buddy are how simple it is to use and pick up. The interface is really nice and makes everything point and click set up. We also really like how easy it is to set up users and limit them to various projects or actions. We have really been able to empower our development team even to a junior level. Last the integrations with Slack and Github have enabled us to notify the whole team when a deployment fails or succeeds.

Inconvénients

If Buddy is down for maintenance (this is extremely rare and also only for a few minutes usually) it can delay our deployments waiting for it to be back up. This isn't even a complaint really but more that it's the only small negative we can think of.

Avantages

I love working in my terminal, but when the UX/UI of a product is as good as this, I love working in a GUI too. The UI is completely intuitive and very fun to use.

From a functionality point of view, the system is incredible. Being able to quickly spin up very complex builds & deployments, and then tie in all sorts of notifications is a dream come true. YML is fine, but being able to tie in all these steps with a visual pipeline editor/builder, is a treat and I thoroughly enjoy using it.

Inconvénients

It's expensive. It's worth every penny, but its still a lot of pennies to pay every month for a small team / freelancer. There is a free plan, but you'll quickly hit the 120 builds per month limit.

Avantages

The best thing about buddy is probably their customer support. The software itself doesn't require to much explanation, but when you do have a suggestion or piece of feedback it is handled with care.

Inconvénients

The activity view per project could have a bit more filtering options and the sandbox option in projects is a bit to expensive for our use.

Avantages

The UI is incredibly easy to use, and functions flawlessly.

Inconvénients

A few additional integrations with other applications would be nice/ideal.

Avantages

Its ease of use, comprehensive set of tools and features for automation, and strong focus on security. Its intuitive user interface and flexible pipeline configurations make it simple for teams to set up and manage their software development processes.

Inconvénients

The pricing could be more affordable. Also I felt that front-end deployment takes longer - wish this could be improved.

Avantages

Once you've configured your standard deployment patterns in yml format, you can simply check any new projects into your SCM and then tell Buddy to create a new project from it. From there, Buddy will pick up your predefined pipelines and GO!

AWS integration is a simple single set up for the entire org acc, no need to each user to have their own access keys stored in Buddy.

As we don't have a DevOps team at our company, deployments are taken care of by the teams. Buddy makes is easy to create, edit and manage these deployments.

Inconvénients

The concurrency based pricing. I would prefer if pricing could be calculated based on actual resource usage as I assume all the build servers are most likely Fargate or scaled EC2 clusters.

In any case, being restricted on concurrency per subscription can be a little annoying, especially on deployment days where I may need to release 10 services simultaneously, but I can only do 2 at a time... each taking around 5 minutes for full blue/green deployment. This means it can take up to an hour to deploy 10 services, where as ideally I want them all deployed within 10 minutes.