Buddy聽vs聽Jenkins

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Buddy
Buddy

172
167
+ 1
566
Jenkins
Jenkins

16K
12.8K
+ 1
2.1K
Add tool

Buddy vs Jenkins: What are the differences?

What is Buddy? Build, test and deploy on push in seconds. Git platform for web and software developers with Docker-based tools for Continuous Integration and Deployment.

What is Jenkins? An extendable open source continuous integration server. In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Buddy belongs to "Continuous Deployment" category of the tech stack, while Jenkins can be primarily classified under "Continuous Integration".

Some of the features offered by Buddy are:

  • Automatic deployments on push to branch
  • Docker-based builds and tests
  • 10-minute setup of complete environment

On the other hand, Jenkins provides the following key features:

  • Easy installation
  • Easy configuration
  • Change set support

"Docker" is the primary reason why developers consider Buddy over the competitors, whereas "Hosted internally" was stated as the key factor in picking Jenkins.

Jenkins is an open source tool with 13.3K GitHub stars and 5.48K GitHub forks. Here's a link to Jenkins's open source repository on GitHub.

Facebook, Netflix, and Instacart are some of the popular companies that use Jenkins, whereas Buddy is used by Docplanner, Buddy, and Ambar. Jenkins has a broader approval, being mentioned in 1774 company stacks & 1526 developers stacks; compared to Buddy, which is listed in 20 company stacks and 13 developer stacks.

- No public GitHub repository available -

What is Buddy?

Git platform for web and software developers with Docker-based tools for Continuous Integration and Deployment.

What is Jenkins?

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Buddy?
Why do developers choose Jenkins?

Sign up to add, upvote and see more prosMake informed product decisions

Sign up to add, upvote and see more consMake informed product decisions

What companies use Buddy?
What companies use Jenkins?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Buddy?
What tools integrate with Jenkins?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Buddy and Jenkins?
AWS CodePipeline
CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.
DeployBot
DeployBot makes it simple to deploy your work anywhere. You can compile or process your code in a Docker container on our infrastructure, and we'll copy it to your servers once everything has been successfully built.
Spinnaker
Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
Google Cloud Build
Cloud Build lets you build software quickly across all languages. Get complete control over defining custom workflows for building, testing, and deploying across multiple environments such as VMs, serverless, Kubernetes, or Firebase.
Deployer
A deployment tool written in PHP with support for popular frameworks out of the box
See all alternatives
Decisions about Buddy and Jenkins
Buddy
Buddy

We use Buddy because it's extremely easy to start working with, because of the powerful GUI which let you configure pipeline in minutes, but also let you switch to the YAML based pipeline, and have full control over your pipeline and deploy cycle. I also appreciate the support by the Buddy team, they are an extraordinary focused team, which are able to act and think as a developer, and this is extremely important!

See more
Buddy
Buddy

I use Buddy because the price was reasonable, the user interface was much more attractive and intuitive, and the pipeline "plugin" approach suited my needs than other services like Jenkins. I have used Buddy for simple Dev Ops processes like running basic SHELL commands within an application to a full scale application deployment with unit testing. I have even been able to use Buddy to deploy applications to other hosting services like Fortrabbit and Heroku.

See more
szekely-szabolcs
szekely-szabolcs
| 2 upvotes 251 views
atRed Rock SolutionsRed Rock Solutions
Buddy
Buddy

I use Buddy because: - It is both simple and complex, modern UI, - ideal for many languages, platforms and various projects - a great plus: nice live chat support (helped me couple of times already - better than surfing the web and looking for solutions). - new features added regularly - and it just works!

See more
Buddy
Buddy

I've been using Buddy extensively during the last year while I was working as CTO in a web agency. Because of the nature of the business, we had projects of all kinds with a big assortment of technologies involved and different delivery platforms. Once we hooked it up to our internal Bitbucket system, we managed to streamline and automate the delivery for more than 35 projects, each one with its own pipelines for building and delivering the software in staging and production environments. Useless to say the tool allowed us to save a huge amount of time and it worked flawlessly on all occasions. I'm a big fan of Buddy, I could not recommend it more and I try to expand the knowledge about this great tool around as much as I can.

See more
Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD | 19 upvotes 877.8K views
Vagrant
Vagrant
VirtualBox
VirtualBox
Ansible
Ansible
Elasticsearch
Elasticsearch
Kibana
Kibana
Logstash
Logstash
TeamCity
TeamCity
Jenkins
Jenkins
Slack
Slack
Apache Maven
Apache Maven
Vault
Vault
Git
Git
Docker
Docker
CircleCI
CircleCI
LXC
LXC
Amazon EC2
Amazon EC2

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Buddy
Buddy

I use Buddy because it's very easy to get started with. The modern UI allows for an easy overview of your projects and pipelines making it a joy to work with. Buddy allows me to focus and really work on the products we're creating and not worry about the small tasks that tend to take up a lot of your time. In short, it's a timesaver and it's very cost-efficient to start with!

See more
Joshua Dean K眉pper
Joshua Dean K眉pper
CEO at Scrayos UG (haftungsbeschr盲nkt) | 7 upvotes 81.4K views
atScrayos UG (haftungsbeschr盲nkt)Scrayos UG (haftungsbeschr盲nkt)
GitLab CI
GitLab CI
GitLab
GitLab
GitLab Pages
GitLab Pages
Jenkins
Jenkins

We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

See more
Sebastian G臋bski
Sebastian G臋bski
CTO at Shedul/Fresha | 4 upvotes 321.9K views
atFresha EngineeringFresha Engineering
CircleCI
CircleCI
Jenkins
Jenkins
Git
Git
GitHub
GitHub
New Relic
New Relic
AppSignal
AppSignal
Sentry
Sentry
Logentries
Logentries

Regarding Continuous Integration - we've started with something very easy to set up - CircleCI , but with time we're adding more & more complex pipelines - we use Jenkins to configure & run those. It's much more effort, but at some point we had to pay for the flexibility we expected. Our source code version control is Git (which probably doesn't require a rationale these days) and we keep repos in GitHub - since the very beginning & we never considered moving out. Our primary monitoring these days is in New Relic (Ruby & SPA apps) and AppSignal (Elixir apps) - we're considering unifying it in New Relic , but this will require some improvements in Elixir app observability. For error reporting we use Sentry (a very popular choice in this class) & we collect our distributed logs using Logentries (to avoid semi-manual handling here).

See more
Epistol
Epistol
Laravel
Laravel
PhpStorm
PhpStorm
Google Analytics
Google Analytics
Sass
Sass
HTML5
HTML5
JavaScript
JavaScript
Vue.js
Vue.js
Webpack
Webpack
Buddy
Buddy
nginx
nginx
Ubuntu
Ubuntu
GitHub
GitHub
Git
Git
Deployer
Deployer
CloudFlare
CloudFlare
Let's Encrypt
Let's Encrypt
Stripe
Stripe
Asana
Asana
Bulma
Bulma
PHP
PHP
#CDG
CDG

I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

See more
Jenkins
Jenkins

I'd recommend to go with Jenkins .

It allows a lot of flexibility and additional plugins that provide extra features, quite often not possible to find elsewhere unless you want to spend time on providing that by yourself.

One of key features are pipelines that allow to easily chain different jobs even across different repos / projects.

The only downside is you have to deploy it by yourself.

See more
Interest over time
Reviews of Buddy and Jenkins
Avatar of czuli
Wordpress
Review ofBuddyBuddy

I like Buddy! They provide a completely free service for hosting, storing, and collaborating on code. Seriously, if you aren't using them, go sign up now.

Review ofBuddyBuddy

Great collaboration-friendly git repository hosting. Plus integration with all sorts of other stuff.

Review ofBuddyBuddy

Allows quick, easy and simple deployments.

How developers use Buddy and Jenkins
Avatar of Kalibrr
Kalibrr uses JenkinsJenkins

All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.

Avatar of Wirkn Inc.
Wirkn Inc. uses JenkinsJenkins

Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.

Avatar of B霉i Thanh
B霉i Thanh uses JenkinsJenkins
  • Continuous Deploy
  • Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
  • Staging and production stages: Build and rollback quicly with Ansistrano playbook
  • Sending messages of job results to Chatwork.
Avatar of AngeloR
AngeloR uses JenkinsJenkins

Currently serves as the location that our QA team builds various automated testing jobs.

At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.

Avatar of Trusted Shops GmbH
Trusted Shops GmbH uses JenkinsJenkins

We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.

Avatar of Volkan 脰z莽elik
Volkan 脰z莽elik uses BuddyBuddy

Buddy is deployment: simplified.

With buddy, you can actually have fun while you deploy your infra.

Beautiful UI, excellent UX, solid product, fanatical support!

Avatar of Ambar
Ambar uses BuddyBuddy

It's our main CI for every project we have

Avatar of Buddy
Buddy uses BuddyBuddy

Build, test & deploy code in seconds

Avatar of Caleb Marcos
Caleb Marcos uses BuddyBuddy

Autodeploy files.

How much does Buddy cost?
How much does Jenkins cost?
Pricing unavailable