When running CloudBees CI on traditional platforms, consult this page for supported platforms.
The following sections detail Java support for CloudBees CI on traditional platforms.
For CloudBees CI on traditional platforms, CloudBees recommends running it as a standalone application installed with one of the following:
java -jar cloudbees-core-cm.war
The native package for Red Hat (
.rpm), Debian/Ubuntu (
.deb) or Windows (
CloudBees also supports running CloudBees CI on traditional platforms 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 for only the following versions:
Oracle JDK 11 - 64 bits
OpenJDK JDK 11 - 64 bits
Oracle JRE / JDK 8 - 64 bits 1
OpenJDK JDK / JRE 8 - 64 bits 1
1 Support for Java 11 was added in version 2.332.1.4. CloudBees strongly recommends that you upgrade your CloudBees CI instance to Java 11 as soon as possible for the best experience.
In a future release, support for Java 8 will be discontinued and you will be unable to run new versions of the product on Java 8 going forward. Releases that occurred during the support window for Java 8 will continue to run on Java 8.
CloudBees Support may ask you to move forward to a specific update release (for example, |
CloudBees endeavors to build plugins against the JDK that corresponds to the minimum Java requirements of the oldest supported CloudBees CI on traditional platforms 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.
CloudBees supports running CloudBees CI on traditional platforms in Docker containers, subject to the following constraints:
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 Kubernetes, OpenShift, Docker Swarm, Mesos, or Amazon ECS.
CloudBees CI on traditional platforms is supported on the following platforms 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).
CloudBees supports the following versions of NFS:
NFS v4.1 and higher
|There are known performance issues with NFS v4.0. CloudBees supports NFS v4.1 and higher, but CloudBees does not support NFS v4.0.|
CloudBees supports Amazon EFS as a storage backend for CloudBees CI. However, like any technology, Amazon EFS comes with tradeoffs that should be explored and understood.
You can use EFS to create a volume available across multiple Availability Zones. However, this comes at the cost of both performance and a higher price. Due to EFS’s nature, it will almost always perform slower than EBS, which some will find unacceptable. For fine-tuning the EFS performance configuration, please refer to Amazon’s documentation: https://aws.amazon.com/premiumsupport/knowledge-center/linux-efs-performance-modes/.
Although rare, customers have encountered issues with the default settings (Burst Credits), resulting in a complete outage of the platform.
If you open a support case about a problem with CloudBees CI on Amazon EFS, we will work with you to ensure that the CloudBees CI product is working correctly. If we believe that the problem is due to the performance of Amazon EFS, we may ask you to open a support case with Amazon to resolve the issue. In some rare situations, the CloudBees CI product may be working as intended, and the CloudBees support ticket may be closed without resolution of the reported problem.
Configuration as Code (CasC) for Controllers is supported in CloudBees CI on traditional platforms as of May 2020.
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
Configuration as Code (CasC) for Controllers in the CloudBees CI on traditional platforms administrator guide
Configuration as Code in the CloudBees Jenkins Distribution administration guide