Supported platforms for CloudBees Core on traditional platforms


When running CloudBees Core on traditional platforms, consult this page for supported platforms.

Java support

The following sections detail Java support for CloudBees Core on traditional platforms.

Supported Java application servers

For CloudBees Core 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 (.msi)

CloudBees also supports running CloudBees Core on traditional platforms on Java application servers with the following requirements:

  1. The WAR application must be the only web application running on the Java application server.

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

Note
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

Not supported

2017-03-01

Apache Tomcat 8.5

v8.5.0

2019-10-31

Apache Tomcat 9.0

9.0.0

Supported JDK versions

CloudBees supports only JDKs or JREs provided by either Oracle or OpenJDK for only the following versions:

  • Oracle JRE / JDK 8 - 64 bits

  • OpenJDK JDK / JRE 8 - 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.

Note
If you 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.

How CloudBees Core is affected by the end of public updates for Oracle Java 8

Oracle Java 8 reaches the end of public updates in December 2020. Java 11 is the next Java LTS. Therefore, CloudBees is actively working to modify CloudBees Core to run on Java 11.

Some of the CloudBees public activities surrounding Java 11 support can be viewed at the Jenkins Platform Special Interest Group.

Until CloudBees Core supports Java 11, CloudBees recommends using either:

  • An actively supported version of OpenJDK 8, such as those maintained by:

Alternately, you may purchase extended support from Oracle for the Oracle 1.8 JVM (EOL in December 2020).

Plugin compatibility

CloudBees endeavors to build plugins against the JDK that corresponds to the minimum Java requirements of the oldest supported CloudBees Core 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.

Supported Docker environments

CloudBees supports running CloudBees Core on traditional platforms in Docker containers, subject to the following constraints:

  1. The Docker image must be the image provided by CloudBees, which is cloudbees/cloudbees-core-cm or cloudbees/cloudbees-core-oc for CloudBees Core on traditional platforms

  2. 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). Container orchestration environments (such as Docker Swarm and Mesos) are consequently not supported.

Supported operating systems

CloudBees Core on traditional platforms is supported on the following platforms as long as the operating system is actively supported by the vendor:

  • Debian

  • Red Hat Enterprise Linux

  • Ubuntu

  • CentOS

  • Fedora

  • openSUSE

  • Microsoft Windows

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

Supported NFS versions

CloudBees supports the following versions of NFS:

  • NFS v.3.x

  • NFS v4.1 and higher

Note
There are known performance issues with NFS v4.0. CloudBees supports NFS v4.1 and higher, but CloudBees does not support NFS v4.0.

Configuration as Code (CasC) support in CloudBees Core on traditional platforms

As of August 2019, the Jenkins Configuration as Code Plugin is not fully supported in CloudBees Core on traditional platforms.

Specific issues with the Jenkins Configuration as Code Plugin within CloudBees Core on traditional platforms include:

  • Enabling the Jenkins Configuration as Code Plugin on CloudBees Core on traditional platforms instances may lead to system instability, because CloudBees products have not been fully tested against the Configuration as Code Plugin.

  • Although it is technically possible to use the Jenkins Configuration as Code Plugin with Client Masters in the CloudBees Core environment, you will not be able to configure:

    • CloudBees proprietary plugins, including those delivered through CAP. The plugin manager will override configuration properties set by the Jenkins Configuration as Code plugin.

    • CloudBees-specific configurations in masters.

    • Any community/open source plugins that do not support or are not compatible with the Jenkins Configuration as Code Plugin.