The unique and intuitive way we can interact with it. It is a complete platform that's also very simple to use, so simple that setting up any new pipeline usually takes ten minutes tops. At our company, we use multiple Buddy actions, such as: File transferring (SFTP), performing Status Checks for CR, building and pushing Docker images, establishing containerized environment for tests and setting up K8s deployment images. And we are pretty happy with our overall experience with Buddy.

Price, maybe? IIRC, it's a little more expensive than alternatives but I think it's worth it in the end.

It just works. With very little setup and maintenance the solution just works. Features are intuitive, controls are plenty, and the UI is beautiful. I started with the free self-hosted version, and have continued with both the cloud and self-hosted on various teams. The various price points are great for getting the entire Git workflow organized for your team.

- 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

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

I

* 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

* 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),

This is a good tool for devops but requires few flexibility of using multiple code repo urls in a project, able to create pipeline automatedly selected branches. Plugins for Liquibase, soanrqube servers etc

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

Selecting only one code repo for a project.

I was responsible to always compare the code before applying on production and BuddyWorks allows me to save time every day. Your interface is beautiful and easy to use. With a few clicks, you can create powerful pipelines.

BuddyWorks allows us to create useful pipeline. You can even pipeline with approbation and testing.

Maybe some aspects of the interface. The cards from each project are too big. If these cards would be smaller I could see all my projects and groups without scrolling the windows.

I really love this product it makes my life easy.

I like a lot the easy way to configure projects and create pipelines to deploy my application in different environments.

I think they should create most documentation.

Fantastic product, support is top-notch. Definately wouldn't consider going anywhere else.

Buddy introduces a very easy to use GUI, rather than composing the YAML file manually. I really like how you can see the progress through the steps, when running a pipeline. This also is worth its weight in gold when it comes to debugging a step or process.

I do feel like the paid plans could be more flexible, maybe add the ability to mix add-ons to plans. For example, adding more projects to a plan or more minutes to allowance. I am pretty frugal and don't like to pay for something if I don't have to. However this is definately worth the investment.

We have been using it for almost 2 years and it's been great. Now we have 66 configured projects and the structure of pipelines makes it easy for us to maintain all these projects at once.

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

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

Great customer support when I started using it, I got guided through a few complex setup steps. When I first started playing with it to feasibility test I had a really complex approach, further reading into the docs allowed me to build a single 5 action pipeline that eliminated approximately 15 manual touch points on the previously deployment process we had.

This is ridiculously easy to use and build very complex pipelines for CI deployments. It has saved huge amounts of dev ops time for use and allows for some quite niche commands to run when we trigger deployments.

Nothing really, I think the price points are very fair for the time it saves, they have a good response rate to support requests and are helpful.

- Sexy UI - Works beautifully - Less stress and time spent on deployments

A few UI quirks here and there, but that's not really a con.

Buddy.works is a comprehensive and user-friendly software that offers a wide range of features for continuous delivery and continuous development. It can automate the process of building, testing, and deploying NodeJS applications to cloud instances. The pipeline management feature in Buddy.works allows for easy creation and management of multiple pipelines, streamlining the development process. By integrating with popular version control systems like Git, Buddy.works allows for easy management of code changes and collaboration with team members. Additionally, it can be integrated with cloud providers like AWS, GCP, and Azure to deploy the NodeJS apps on the cloud instances. Overall, Buddy.works is a great tool for automating the software development process, specifically for NodeJS apps deployment on cloud instances with CI/CD.

Buddy.works is a comprehensive and user-friendly software that offers a wide range of features for continuous delivery, pipeline management, and continuous development. One of the things I liked most about the software is its ability to automate the delivery process, making it easy to deploy updates and new features to users. The pipeline management feature is also very impactful, allowing users to easily create and manage multiple pipelines, streamlining the development process. The software is also very easy to use, with a user-friendly interface and a comprehensive set of tools for continuous development. Additionally, integration with existing business processes was a breeze, thanks to the software's robust integration capabilities with a wide range of third-party tools and services.

As a user of Buddy.works, I found that one of the cons of the software is the lack of flexibility in customizing the pipeline management feature. While it's easy to create and manage multiple pipelines, I would have liked more options for customizing and adapting the pipelines to my specific needs. Additionally, I found that the user interface can be a bit overwhelming at times, with multiple menus and options that can be difficult to navigate. I also felt that some features, such as configuration management, could be improved to provide more detailed and granular control. However, despite these cons, I found that integration with my existing business processes was relatively easy and the software provided a comprehensive set of tools for continuous development.

We use Buddy Works to deploy new updates of LMS-kind software to our development and production servers in real-time

This service is a beast, from the way you start configuring your pipeline from an existing repository and all the available actions to the fully specified real-time log of the executed actions, the ability to clone existing pipelines and the analytics provided and the possibility to rollback

The only thing that we didn't like was the quantity of projects that you can have in the free version but that doesn't justify the overall quality of the service

Wonderful

The easy way we can set-up a pipeline to deploy products (api, smartphone apps, website)It take 10x less time than on other platforms

The price and the lack of visibility about account consumption

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

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.

As a dev agency with over 100+ websites, Buddy has made it simple to deploy to production/staging servers with ease.

Ease of use! If you're not into writing configuration code, Buddy has an excellent GUI setup that guides you through deployment setups.

Transfering repositories from GUI setup to a .yaml setup can be a hassle if buddy doesn't pick up the new buddy.yaml file. I'm probably doing something wrong though.

Overall, very good. We've had a few little niggles here and there but support has solved them within a day or two at most. I love the fact that I can create and deploy a new microservice in under 30 minutes!

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.

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.

I'm using it mainly to deploy Laravel projects and with Buddy that saves me a lot of time.

It's so easy to create a new project and setup the actions needed for deployment. What I also like is the possibility to clone a project and to setup variables within a project.

That's not really about the product itself, but about the pricing. I'm still on an old plan, but now even the smallest plan starts at $75/month. That's quite expensive if you have just a couple of projects.

Buddy makes it easy to setup different pipelines for your staging and production servers. There are a large selection of pipeline actions available - integrations and tools to fit everyone's workflow. The Buddy interface is easy to navigate and the team has evidently put a lot of care into their product.

I can't think of any big cons off the top of my head. Maybe one thing is that the pricing can be kinda steep, especially if you're a really small team or a freelancer.

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

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

Overall, we've seen great increases in deployment speed and ability to get code from Development to Production quickly and efficiently.

We love the stability it has provided as well as consistently deploying our code, both compiled and 'raw' to all of our services.

We've occasionally had glitches in deployment, but these were rectified very quickly and communicated to us by the team at Buddy.

Before Buddy, we relied on tools like DeployBot to automate our deployments. Buddy is better in every conceivable way, and it doesn't require a PhD in Computer Science to setup or force you to structure your app in a specific way. We have it doing: Dependency installs Asset generation Atomic deployments Elastic Beanstalk deployments Cloudflare / Cloudfront cache clears Etc

Lightning fast Extremely flexible - you can basically create any pipeline you can dream of

Support can be a bit sluggish due to time zone issues and the capability of the first responders in chat.

It is a great way to handle our deployments while it remains simple and easy to use. Even more importantly when it came to stepping up a level and starting working with ansistrano and much more advanced deployment systems it stood its ground.

Literally nothing, it's a great piece of software.

Buddy has helped our team tremendously in making us able to collaborate on site development.

ease of use, efficiency, accessibility, and design.

learning curve, there are still some features that I am discovering through use - would be nice to have courses on quickly setting up all the applications of Buddy

Buddy.works is an important tool for our deployment!

The navigation is sometimes not self-explaining. Change the owner of the workspace you can find unter "Billing".