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.
The following sections detail Java support for CloudBees Jenkins Distribution.
For CloudBees Jenkins Distribution, CloudBees recommends running it as a standalone application installed with one of the following:
java -jar cloudbees-jenkins-distribution.war
The native package for Red Hat (
.rpm), Debian/Ubuntu (
.deb) or Windows (
CloudBees also supports running CloudBees Jenkins Distribution on Java application servers with the following requirements:
The WAR application must be the only web application running on the Java application server.
The restart capabilities of the application server must not be used; the instance must be restarted either via the JVM or using the instance’s built-in restart function.
|CloudBees only supports two versions of Apache Tomcat and strives to support the latest GA version.|
|Application Server||Minimum Version||End Of Support|
Apache Tomcat 8.0 and lower
Apache Tomcat 8.5
Apache Tomcat 9.0
CloudBees supports only JDKs or JREs provided by either Oracle or OpenJDK (either from OpenJDK or Red Hat) for the following versions:
Oracle JRE / JDK 8 - 64 bits
Oracle JDK 11 - 64 bits
OpenJDK JDK / JRE 8 - 64 bits
OpenJDK JDK 11 - 64 bits
In some cases, to fix a problem, CloudBees may occasionally require you to move forward to a specific update release (for example,
_uXX) of a currently supported JDK/JRE version.
|If you are not running a supported JDK version, CloudBees Support may ask you to move to a supported JDK version before diagnosing your problem. If you are running an outdated version of a supported JDK, CloudBees Support may ask you to move to a more recent JDK version since the more recent version may benefit from bug fixes and performance improvements. CloudBees recommends you keep your JDK version up-to-date.|
Oracle Java 8 reaches the end of public updates in December 2020.
CloudBees endeavors to build plugins against the JDK that corresponds to the minimum Java requirements of the oldest supported CloudBees Jenkins Distribution version.
CloudBees tests its binaries and plugins against the supported JDKs.
Some third party plugins may have different requirements which are outside of CloudBees control. Where a third party plugin is bundled within a CloudBees product, CloudBees endeavor to ensure that the plugins’ Java requirements are compatible with our supported Java versions.
|If you are using a plugin that is not in the CloudBees Assurance Program, be sure that you are using the most recent possible version of the plugin.|
CloudBees supports running CloudBees Jenkins Distribution in Docker containers, subject to the following constraints:
The Docker image must be the image provided by CloudBees, which is cloudbees/cloudbees-jenkins-distribution for CloudBees Jenkins Distribution
The Docker Engine used to run these containers must run on a Linux platform and must be a standalone Docker Engine provided by Docker, Inc. or by a Linux distribution provider (such as Red Hat or CentOS).
The Docker environment cannot be managed by a container orchestration tool or cluster manager such as Docker Swarm, Mesos or Amazon ECS. CloudBees supports the installation in Kubernetes under the premises explained in Installing on Kubernetes.
CloudBees Jenkins Distribution is supported on the following operating systems as long as the operating system is actively supported by the vendor:
Red Hat Enterprise Linux
There are no universally applicable OS-level requirements. Some customers find that they need to increase the per-process open files limit on Linux (
ulimit -n); or increase the maximum size of the Java heap or permanent generation (refer to JVM tuning guides for specifics).
For CloudBees Jenkins Distribution, CloudBees supports Kubernetes 1.x, starting with 1.11, as long as it is actively supported by the Kubernetes distribution provider and is one of the following implementations:
The version used must be Generally Available. CloudBees does not support or recommend "proof of concept" offering of Kubernetes platforms or Beta or Public preview versions.
CloudBees Jenkins Distribution might work on other Kubernetes implementations such as Azure Kubernetes Service (AKS) or Google Kubernetes Engine (GKE) if it is installed as a Kubernetes Helm Chart, but CloudBees does not fully support these platforms. Red Hat OpenShift is not supported for the moment.
CloudBees only supports CloudBees Jenkins Distribution on Kubernetes when it is installed using the official CloudBees Jenkins Distribution Helm charts.
CloudBees supports only production releases of Helm: RC, beta, patch or experimental releases of Helm are not supported.
Starting with CloudBees CI on modern cloud platforms version 220.127.116.11, Helm version 3.0.2 or later is supported.
We recommend that you migrate to Helm V3 as soon as possible. Support of Helm V2 was deprecated in July 2020.
As of August 2019, the Configuration as Code Plugin is supported as a Preview for CloudBees Jenkins Distribution.
Documentation for Configuration as Code with CloudBees Jenkins Distribution is published as Configuration as Code in CloudBees Jenkins Distribution. This page also contains quick-start instructions and known limitations.
A Preview feature:
Has not undergone end-to-end testing with CloudBees products
Is provided without service-level agreements (SLA) and therefore does not include CloudBees' commitment on functionality or performance
May impact other stable areas of the product when used
May have limited documentation
May not be feature complete during the Preview period
May graduate from preview state to fully supported or be removed from the product
May introduce incompatible, backward-breaking changes that could revoke the ability to upgrade
The following plugins support Configuration as Code (CasC).
If you don’t see a plugin in this list, this can mean one of two things: that plugin does not support CasC or that plugin does not require configuration.
This list of plugins applies to CloudBees CI, CloudBees Jenkins Distribution, and CloudBees Jenkins Platform.
|Configuration as Code is not supported on CloudBees operations center.|
|Plugin Name||Minimum version||Configuration example|
https://github.com/jenkinsci/jira-plugin/blob/master/src/test/resources/hudson/plugins/jira/single-site.yml and https://github.com/jenkinsci/jira-plugin/blob/master/src/test/resources/hudson/plugins/jira/multiple-sites.yml