Buddy VS Artifactory

Buddy Reviews

1. firomero    

   Developer at Codechanic | about 3 years ago
   Buddy Rocks

   I have around two years when met buddy for my personal projects. I found it intuitive and great. I almost can set up pipelines with closed eyes. It helped me with development and learning. I recommend also startups and mature projects.

   🏁 Competitors: Jenkins

   👍 Pros:    Intuitive|Easy to use|Verbose|Great user experience

   👎 Cons:    A bit expensive
2. Jalib Hussain Khan    

   Software Engineer at All Resource Technologies | about 3 years ago
   Best there ever was

   Buddy works is the most awesome automating CI application, it lets you deploy sites at the best convenience. It also automatically detects the type of language your application uses and gives you the recommendation regarding the commands which should be executed

   🏁 Competitors: CircleCI, Codeship, Travis CI
3. Lucas Pereira    

   CTO at Tezus | about 3 years ago
   The best solution for continuous delivery

   I have a eCommerce company and the Buddy helps us to delivery all projects and maintain the our platform updated. The Buddy is easy to implements and easy to operate, definitively, the best solution

   🏁 Competitors: CircleCI, Travis CI

   👍 Pros:    Easy to use|Easy user interface|Easy integration|Fast|Database documentation|Tools integrations|Visual

   👎 Cons:    Higher base price

Artifactory Reviews

Buddy mentions (10)

• Most Useful CI/CD Tools for DevOps

  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 / 23 days ago

• We use GitHub Actions to build GitHub

  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 / about 2 years ago

• Learn to push an empty commit

  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 / over 2 years ago

• Free for dev - list of software (SaaS, PaaS, IaaS, etc.)

  Buddy.works — A CI/CD with 5 free projects and 1 concurrent runs (120 executions/month). - Source: dev.to / almost 3 years ago

• Hide & Seek Code: Part II

  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 / almost 3 years ago

Artifactory mentions (20)

• Where to store executables shared by a team/project

  I kind of hate it, but Artifactory seems popular at companies: https://jfrog.com/artifactory/. Source: 10 months ago

• Adding Virtual Environments to Git Repo

  When not providing all dependencies yourself, you might suffer from people deleting the packages you depend on (IMHO a very rare scenario). If it is really that critical (hint: usually it isn't), create a local mirror of Pypi (full or only the packages you need). Devpi, Artifactory, etc. Can do that or you just dump the necessary files into Cloud storage, so you have a backup. Source: about 1 year ago

• Authenticated Docker Hub image pulls in Kubernetes

  Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago

• Concretely, how do you trust the experts? That is, how do you a) identify experts relevant to something and b) determine if they have a consensus (and if so, what it is) on a given topic?

  Like suppose for a second that . . . Idk . . . a product team wants our ci workflows to start using Artifactory. Okay great, I don't know Artifactory integration but I'm going to tell them "Sure, I'll get right on that.". Source: about 1 year ago

• What do I do with large "asset" files?

  If these "assets" have an independent release schedule I would treat them separately (especially if they are externally provided). If they are not built from source then treat them as artefacts, they don't belong in git. You can store the in an artefact repository (like Artifactory of Nexus) or (as u/nekokattt points out) in something like S3. Source: over 1 year ago