CloudBees Jenkins Distribution installation guide

3 minute read

CloudBees no longer supports CloudBees Jenkins Distribution as of February 24, 2021. Please refer to the following step-by-step documentation for Migrating from CloudBees Jenkins Distribution to Jenkins LTS. The increased alignment between CloudBees Jenkins Distribution and Jenkins means users will experience zero impact to Pipeline execution. Existing customers can also contact CloudBees Support to help ensure a smooth transition.

Please see About the CloudBees Jenkins Distribution retirement for more information.

What is CloudBees Jenkins Distribution?

CloudBees Jenkins Distribution provides development teams with a highly dependable, secure Jenkins environment curated from the most recent supported Jenkins release. The distribution comes with a recommended catalog of tested plugins available through the CloudBees Assurance Program.

Upgrades are now a smooth, seamless experience with the BeeKeeper Upgrade Assistant.

The Beekeeper Upgrade Assistant works in parallel with the CloudBees Assurance Program to provide a centralized view of the monitored Jenkins plugins, as well as recommended actions and configuration options.

The free Jenkins Health Advisor by CloudBees plugin keeps an eye out for potential issues and recommendations and sends you email notifications with suggestions tailored to your installation.

CloudBees Jenkins Distribution considerably simplifies the installation and configuration process, and Configuration as Code makes the configuration of CloudBees Jenkins Distribution even easier. With Configuration as Code, you can turn complex configurations into easily-replicated, human-readable code files, and you can manage those configuration files with source control tools like GitHub.

The CloudBees Jenkins Distribution License Report lists the included plugins.

If you are already using Jenkins LTS, refer to Migrating from Jenkins LTS to CloudBees Jenkins Distribution if you are interesting in using CloudBees Jenkins Distribution.

Available platforms

CloudBees Jenkins Distribution is available as a standalone WAR file, which can run in practically any Java runtime environment. CloudBees provides installation packages for the following platforms:

  • Debian or Ubuntu

  • Red Hat Enterprise Linux, CentOS, Fedora

  • openSUSE or SUSE Linux

  • Microsoft Windows

CloudBees Jenkins Distribution can be installed on Kubernetes clusters as well. For instructions, see Installing on Kubernetes.

Installation steps

Installing CloudBees Jenkins Distribution involves the following steps:

  • Downloading and installing the CloudBees Jenkins Distribution package, Docker image, or WAR file

  • Using the Getting Started wizard to set up the plugins and first admin account.

Distribution packages are available at the CloudBees Jenkins Distribution download site.

System requirements for CloudBees Jenkins Distribution

CloudBees Jenkins Distribution requires at least 512 MB of RAM and 2 GB of disk space. The recommend system requirements of at least 4 GB of RAM and 50 GB+ of free disk space provide room to grow with workloads.

There are no universally applicable operating system-level requirements, but depending on the workload placed on the instance, your instance may require changes to certain tunable parameters like heap size or open file descriptor limits.


You must have an installed and configured Docker environment to use the Docker image.


The native packages and Docker containers for CloudBees Jenkins Distribution include a Java runtime environment. Administrators wishing to run the WAR file on its own, or deploy CloudBees Jenkins Distribution in a Java Servlet Container should bear in mind that CloudBees supports:

  • Oracle JRE 8

  • Oracle JDK 11 (CloudBees Jenkins Distribution versions 2.164 and later only)

  • OpenJDK JRE 8

  • OpenJDK JDK 11 (CloudBees Jenkins Distribution versions 2.164 and later only)

Older systems

CloudBees Jenkins Distribution may run on older, non-supported Java runtime environments. Administrators running older versions of Java should expect best effort support for any potential technical issues which may arise. Please refer to the Supported Platforms page for more detailed information.