Supported platforms for CloudBees CI on traditional platforms

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

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

CloudBees distributes Docker container images for ARM64 architecture for CloudBees CI on traditional platforms.

CloudBees CI on traditional platforms is supported on Linux distributions and Microsoft Windows as long as the operating system version is actively supported by a vendor (e.g. 'Standard support', 'Active support', 'Full support' are common terms used, this does not include Legacy support or extended update support subscriptions), and it has a Supported Java version.

Additionally, if you require the service to launch automatically on Linux, systemd must be available.

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 does not support Microsoft CIFS/SMB network filesystems. This is due to known Java issues with file locking on CIFS that cause problematic behavior.

CloudBees supports the following versions of NFS:

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.

High Availability (HA) on a Windows environment is not supported.

CloudBees CI supports Internet Protocol version 6 (IPv6) with the following considerations.

The following third-party tools that interact with the following CloudBees CI plugins do not support IPv6:

CloudBees CI relies on the standard Java platform behavior with regards to the handling of IPv4/IPv6. For more information, refer to Networking properties. If you want Java to establish connections over IPv6 instead of IPv4, you should add the argument -Djava.net.preferIPv6Addresses=true in the Java command line that is passed to start a CloudBees CI component (operations center or controller).

Configuration as Code 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.

CloudBees CI only supports the following web browsers:

CloudBees supports client controllers that run the same version as the operations center or any earlier version that was supported when that version of the operations center was released.

As an example, when CloudBees CI on traditional platforms 2.346.1.4 was released, versions 2.277.4.4 through 2.346.1.4 were supported. CloudBees supports connecting any controller within that range to version 2.346.1.4 operations center. For more information about the support lifecycle, refer to CloudBees maintenance lifecycle policies.

CloudBees supports upgrading CloudBees CI to a version up to one year later than your current version.

As an example, if you are running CloudBees CI on traditional platforms 2.263.4.2, that was released on February 26, 2021, you should first upgrade both your operations center and any controllers to a version up to one year later, such as CloudBees CI on traditional platforms 2.319.3.4, that was released on February 15, 2022. When that upgrade is successful, you can upgrade again to a version up to one year later.

CloudBees support can help you plan and prepare for your upgrade, for more information, refer to Required Data: Assisted Update.