CloudBees聽vs聽Jenkins

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

CloudBees

67
119
+ 1
4
Jenkins

39.3K
31.9K
+ 1
2.2K
Add tool

CloudBees vs Jenkins: What are the differences?

What is CloudBees? Enterprise Jenkins and DevOps. Enables organizations to build, test and deploy applications to production, utilizing continuous delivery practices. They are focused solely on Jenkins as a tool for continuous delivery both on-premises and in the cloud.

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.

CloudBees can be classified as a tool in the "Platform as a Service" category, while Jenkins is grouped under "Continuous Integration".

Some of the features offered by CloudBees are:

  • Hosted CI/CD as a Service
  • Flexible and governed software delivery automation
  • Starter Kit

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

  • Easy installation
  • Easy configuration
  • Change set support

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 CloudBees is used by Netflix, Randstad, and Watchguard Technologies, Inc.. Jenkins has a broader approval, being mentioned in 1775 company stacks & 1529 developers stacks; compared to CloudBees, which is listed in 3 company stacks and 4 developer stacks.

Advice on CloudBees and Jenkins
Needs advice
on
Jenkins
and
Azure Pipelines

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
GitHub

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 Axceligent Solutions | 3 upvotes 路 167.2K views
Needs advice
on
Jenkins
and
GoCD

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 路 154.7K views

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

See more
Needs advice
on
Jenkins
and
Concourse

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 路 73.2K views
Recommends
Concourse

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
Decisions about CloudBees and Jenkins

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
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of CloudBees
Pros of Jenkins
  • 4
    Jenkins
  • 521
    Hosted internally
  • 463
    Free open source
  • 313
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 208
    Rich set of plugins with good documentation
  • 108
    Has support for build pipelines
  • 72
    Open source and tons of integrations
  • 63
    Easy setup
  • 61
    It is open-source
  • 54
    Workflow plugin
  • 11
    Configuration as code
  • 10
    Very powerful tool
  • 9
    Many Plugins
  • 8
    Great flexibility
  • 8
    Git and Maven integration is better
  • 7
    Continuous Integration
  • 6
    Github integration
  • 6
    Slack Integration (plugin)
  • 5
    100% free and open source
  • 5
    Self-hosted GitLab Integration (plugin)
  • 5
    Easy customisation
  • 4
    Docker support
  • 3
    Pipeline API
  • 3
    Excellent docker integration
  • 3
    Platform idnependency
  • 3
    Fast builds
  • 2
    Hosted Externally
  • 2
    It`w worked
  • 2
    Can be run as a Docker container
  • 2
    Customizable
  • 2
    AWS Integration
  • 2
    It's Everywhere
  • 2
    JOBDSL
  • 1
    NodeJS Support
  • 1
    PHP Support
  • 1
    Ruby/Rails Support
  • 1
    Universal controller
  • 1
    Easily extendable with seamless integration
  • 1
    Build PR Branch Only

Sign up to add or upvote prosMake informed product decisions

Cons of CloudBees
Cons of Jenkins
    Be the first to leave a con
    • 12
      Workarounds needed for basic requirements
    • 8
      Groovy with cumbersome syntax
    • 6
      Plugins compatibility issues
    • 6
      Limited abilities with declarative pipelines
    • 5
      Lack of support
    • 4
      No YAML syntax
    • 2
      Too tied to plugins versions

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is CloudBees?

    Enables organizations to build, test and deploy applications to production, utilizing continuous delivery practices. They are focused solely on Jenkins as a tool for continuous delivery both on-premises and in the cloud.

    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 CloudBees?
    What companies use Jenkins?
    See which teams inside your own company are using CloudBees or Jenkins.
    Sign up for Private StackShareLearn More

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

    What tools integrate with CloudBees?
    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

    +7
    3
    1395
    +4
    4
    1683
    +2
    2
    940
    +3
    6
    895
    Dec 4 2019 at 8:01PM

    Pinterest

    +4
    5
    2901
    What are some alternatives to CloudBees and Jenkins?
    CircleCI
    Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
    Bamboo
    Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
    Azure DevOps
    Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
    GitLab
    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
    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.
    See all alternatives
    How developers use CloudBees and Jenkins
    Kalibrr uses
    Jenkins

    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.

    Wirkn Inc. uses
    Jenkins

    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.

    B霉i Thanh uses
    Jenkins
    • 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.
    AngeloR uses
    Jenkins

    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.

    Trusted Shops GmbH uses
    Jenkins

    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.