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

Buddy

299
348
+ 1
606
Jenkins

58.2K
49.7K
+ 1
2.2K
Add tool

Buddy vs Jenkins: What are the differences?

Key Differences between Buddy and Jenkins

Buddy and Jenkins are both popular continuous integration/continuous deployment (CI/CD) tools commonly used in software development pipelines. While they serve similar purposes, there are several key differences that set them apart from each other.

  1. User Interface: Buddy provides a modern and visually appealing user interface that is intuitive and user-friendly. It offers a more polished UI design with various customization options for ease of use. On the other hand, Jenkins has a more dated and less user-friendly interface that requires more technical expertise to navigate and configure.

  2. Deployment Speed: Buddy is known for its fast and efficient deployment speed. It utilizes a highly optimized CI/CD process that allows for quick execution and deployment of software changes. In contrast, Jenkins can be slower in terms of deployment due to its more complex setup and configuration process.

  3. Integration and Plugins: Buddy offers a wide range of integrations and plugins to enhance the development and deployment process. It seamlessly integrates with popular tools and platforms such as Slack, AWS, Azure, and Docker. While Jenkins also provides integration capabilities, it often requires additional plugins and configurations to achieve the same level of compatibility.

  4. Ease of Setup: Buddy simplifies the setup process by providing a user-friendly interface for configuring pipelines and automating workflows. It offers predefined actions and templates, making it easier for developers to get started. Jenkins, on the other hand, requires more configuration and setup expertise, often involving scripting and complex configurations.

  5. Scalability: Buddy is designed to handle scalability with ease. It can efficiently handle parallelism and multiple deployments simultaneously, enabling teams to scale their development processes as needed. Jenkins, although capable of scaling, may require additional infrastructure and configurations to achieve the same level of scalability.

  6. Pricing Model: Buddy offers a straightforward and transparent pricing model based on the number of executions, which allows for more predictable costs. Jenkins, being an open-source tool, is free to use but may incur additional costs for infrastructure and maintenance depending on the setup.

In summary, Buddy provides a user-friendly interface, faster deployment speed, seamless integrations, simplified setup, scalability, and a transparent pricing model compared to Jenkins.

Advice on Buddy and Jenkins
Needs advice
on
Azure PipelinesAzure Pipelines
and
JenkinsJenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

See more
Replies (1)
Recommends
on
GitHubGitHub

If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions

See more
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 519K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 501.8K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Needs advice
on
ConcourseConcourse
and
JenkinsJenkins

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 420.9K views
Recommends
on
ConcourseConcourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

See more
Replies (6)
Dustin Falgout
Senior Developer at Elegant Themes · | 13 upvotes · 575.6K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit · | 9 upvotes · 889.6K views
Recommends
on
Travis CITravis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more
Recommends
on
Google Cloud BuildGoogle Cloud Build

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
on
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
on
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
on
BuildkiteBuildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about Buddy and Jenkins
Stephen Badger | Vital Beats
Senior DevOps Engineer at Vital Beats · | 2 upvotes · 228.8K views

Within our deployment pipeline, we have a need to deploy to multiple customer environments, and manage secrets specifically in a way that integrates well with AWS, Kubernetes Secrets, Terraform and our pipelines ourselves.

Jenkins offered us the ability to choose one of a number of credentials/secrets management approaches, and models secrets as a more dynamic concept that GitHub Actions provided.

Additionally, we are operating Jenkins within our development Kubernetes cluster as a kind of system-wide orchestrator, allowing us to use Kubernetes pods as build agents, avoiding the ongoing direct costs associated with GitHub Actions minutes / per-user pricing. Obviously as a consequence we take on the indirect costs of maintain Jenkins itself, patching it, upgrading etc. However our experience with managing Jenkins via Kubernetes and declarative Jenkins configuration has led us to believe that this cost is small, particularly as the majority of actual building and testing is handled inside docker containers and Kubernetes, alleviating the need for less supported plugins that may make Jenkins administration more difficult.

See more

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Buddy
Pros of Jenkins
  • 56
    Easy setup
  • 53
    Docker
  • 50
    Continuous Integration
  • 49
    Integrations
  • 46
    Beautiful dashboard
  • 45
    Git hosting
  • 43
    Free
  • 42
    Unlimited pipelines
  • 39
    Monitoring
  • 39
    Backup
  • 37
    Great UX
  • 32
    On-Premises
  • 31
    Awesome support
  • 6
    AWS Integrations
  • 5
    Great UI
  • 3
    Hosted internally (Enterprise)
  • 3
    Slack integration
  • 3
    Continuous deployment
  • 3
    Simple deployments
  • 3
    Bitbucket integration
  • 2
    Github integration
  • 2
    UI and YML configuration
  • 2
    Node.js support
  • 2
    Azure integration
  • 2
    Amazing + free
  • 1
    Support for build pipelines
  • 1
    Docker support
  • 1
    Gitlab integration
  • 1
    Android support
  • 1
    Pushover integration
  • 1
    DigitalOcean integration
  • 1
    UpCloud integration
  • 1
    Shopify integration
  • 0
    New Relic integration
  • 0
    Rollbar integration
  • 0
    Sentry integration
  • 0
    Loggly integration
  • 0
    Datadog integration
  • 0
    Bugsnag integration
  • 0
    Honeybadger integration
  • 0
    Telegram integration
  • 0
    HipChat integration
  • 0
    Discord integration
  • 0
    Pushbulet integration
  • 0
    AWS integration
  • 0
    Slack Integration
  • 0
    Google Cloud integration
  • 0
    Heroku integration
  • 0
    Rackspace integration
  • 0
    Kubernetes support
  • 523
    Hosted internally
  • 469
    Free open source
  • 318
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 211
    Rich set of plugins with good documentation
  • 111
    Has support for build pipelines
  • 68
    Easy setup
  • 66
    It is open-source
  • 53
    Workflow plugin
  • 13
    Configuration as code
  • 12
    Very powerful tool
  • 11
    Many Plugins
  • 10
    Continuous Integration
  • 10
    Great flexibility
  • 9
    Git and Maven integration is better
  • 8
    100% free and open source
  • 7
    Github integration
  • 7
    Slack Integration (plugin)
  • 6
    Easy customisation
  • 6
    Self-hosted GitLab Integration (plugin)
  • 5
    Docker support
  • 5
    Pipeline API
  • 4
    Fast builds
  • 4
    Platform idnependency
  • 4
    Hosted Externally
  • 4
    Excellent docker integration
  • 3
    It`w worked
  • 3
    Customizable
  • 3
    Can be run as a Docker container
  • 3
    It's Everywhere
  • 3
    JOBDSL
  • 3
    AWS Integration
  • 2
    Easily extendable with seamless integration
  • 2
    PHP Support
  • 2
    Build PR Branch Only
  • 2
    NodeJS Support
  • 2
    Ruby/Rails Support
  • 2
    Universal controller
  • 2
    Loose Coupling

Sign up to add or upvote prosMake informed product decisions

Cons of Buddy
Cons of Jenkins
  • 1
    Deleted account after 1 month of not pushing code
  • 13
    Workarounds needed for basic requirements
  • 10
    Groovy with cumbersome syntax
  • 8
    Plugins compatibility issues
  • 7
    Lack of support
  • 7
    Limited abilities with declarative pipelines
  • 5
    No YAML syntax
  • 4
    Too tied to plugins versions

Sign up to add or upvote consMake informed product decisions

- 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.

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

What companies use Buddy?
What companies use Jenkins?
Manage your open source components, licenses, and vulnerabilities
Learn More

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

Blog Posts

Mar 24 2021 at 12:57PM

Pinterest

GitJenkinsKafka+7
3
2191
GitJenkinsGroovy+4
4
2766
Dec 4 2019 at 8:01PM

Pinterest

KubernetesJenkinsTensorFlow+4
5
3328
GitGitHubPython+22
17
14268
JavaScriptGitHubPython+42
53
22089
What are some alternatives to Buddy and Jenkins?
Git
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
Visual Studio Code
Build and debug modern web and cloud applications. Code is free and available on your favorite platform - Linux, Mac OSX, and Windows.
Docker
The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
npm
npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day.
See all alternatives