Buddy CI/CD is an automation platform designed to streamline and accelerate software development and deployment processes. By emphasizing simplicity and efficiency, Buddy offers an intuitive UI that allows teams to set up, monitor, and execute pipelines with minimal friction.

– Source: dev.to
/
5 months ago

We switched to buddy.works[0] about a year ago and honestly it’s just been… smooth. The UI is just great, the wealth and breadth of options is ever increasing and all the basics like knowing what went wrong, restarting, debugging, duplicating etc just work as you’d expect. One of the few companies I can recommend. [0] https://buddy.works.

– Source: Hacker News
/
over 2 years ago

For continuous integration, we are using Buddy delivery pipelines which allow us to build, test and deploy applications on a single push to a specific git branch. It helps us to reduce the manual overhead of deploying code to the server and handle all the actions automatically.

– Source: dev.to
/
almost 3 years ago

Buddy.works — A CI/CD with 5 free projects and 1 concurrent runs (120 executions/month).

– Source: dev.to
/
about 3 years ago

That is when we found out about Buddy. Buddy is one of those easy DIY devops tools out there. Best part is the UI and how easy it is to create a deployment pipeline.

– Source: dev.to
/
over 3 years ago

Tried all kinds of things. Doing manual uploads to a Digitalocean droplet. Custom CI pipelines via https://buddy.works, Forge, Ploi.
I’d say choose whatever makes it the easiest (although there is good learning experience to be made from making a pipeline yourself) to maintain. Currently using https://ploi.io to manage the servers and deployments for my Laravel apps and running them on cheap $5 Digitalocean Droplets.

Source:
over 3 years ago

Best way to move is putting all of the code on local into a git repo, committing to gitlab or github, and using something like Buddy Works to push the code on commit. If you’re not familiar with git yet, then moving code via SFTP is also an option.

Source:
over 3 years ago

Continuous integration and deployment is a fun topic. I’ve learned a lot recently working on some projects at my actual job.

The task can be a little intimidating sometimes, specially if you work with Jenkins. Don’t get me wrong! Jenkins is an amazing tool. I just find the learning curve a little bit steeper compared to other solutions I’ve tried (Github Actions, Gitlab CI/CD Pipelines, Buddy.works, etc).

– Source: dev.to
/
over 3 years ago

I’ve seen some recommendations for DeployHQ and Buddy. Not sure which would be better.

Source:
over 3 years ago

I came across buddy.works and I kinda like it but then the memory is kinda limiting on the free plan and the actual reason I chose buddy was that it allows maintaining a mirror of the repository and I can push to it’s remote to trigger a build but the it failed on all the builds due to memory limitations and I was thinking if there’s other CI/CDs that provide this kind of functionality where I can push a mirror…

– Source: dev.to
/
over 3 years ago