When running CloudBees CI on modern cloud platforms, consult this page for supported platforms.
CloudBees supports running CloudBees CI on modern cloud platforms on:
Kubernetes reference platforms
Amazon Elastic Kubernetes Service (EKS)
Azure Kubernetes Service (AKS)
Google Kubernetes Engine (GKE)
VMware Tanzu Kubernetes Grid Integrated Edition (TKGI)
Red Hat OpenShift Container Platform (OCP) 3.11
Red Hat OpenShift Container Platform (OCP) 4.2, starting with CloudBees CI on modern cloud platforms version 18.104.22.168
Red Hat OpenShift Container Platform (OCP) 4.3-4.6, starting with CloudBees CI on modern cloud platforms version 22.214.171.124
Red Hat OpenShift Container Platform (OCP) 4.7, starting with CloudBees CI on modern cloud platforms version 2.263.4.2
CNCF-certified Kubernetes, versions 1.14 through 1.20. See Certified Kubernetes for information about CNCF-certified Kubernetes.
The following criteria are required for the above supported Kubernetes platforms:
The version is Generally Available.
CloudBees does not support or recommend "proof of concept" offerings of Kubernetes platforms or Beta or Public preview versions.
The version is actively supported by the Kubernetes distribution provider.
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 126.96.36.199, 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 CloudBees CI on modern cloud platforms version 188.8.131.52, CloudBees CI on modern cloud platforms supports Microsoft Windows containers for Kubernetes 1.x starting with version 1.14. However, you can only run CloudBees CI on modern cloud platforms agents in Windows containers. Running controllers or the operations center on Microsoft Windows containers in Kubernetes is not supported. Each cloud provider has various levels of support for Kubernetes features, including Windows containers, so confirm the status with your cloud platform provider.
As of CloudBees CI on modern cloud platforms version 2.263.4.1, Microsoft Windows LTSC 2019 (version 1809) is supported for agents running on Google Kubernetes Engine (GKE) clusters, but not for the operations center or controllers. If running Windows workloads with agents on a GKE cluster, the image provided by CloudBees CI on modern cloud platforms only works on version 1809 of Windows LTSC.
This feature is documented in Managing agents - Running CloudBees CI build agents in Windows containers.
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 modern cloud 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
CloudBees CI on modern cloud platforms controllers run in a set of Docker containers that come pre-configured with OpenJDK 8. CloudBees does not support the modification of these containers.
If you build your own container images for agents, CloudBees recommends using 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
|If your agents are not running a recommended JDK version, CloudBees Support may ask you to move to one before diagnosing your problem. If you are running an outdated version of a recommended JDK, CloudBees Support may ask you to move to a more recent version since the more recent version may benefit from bug fixes and performance improvements. CloudBees recommends that you keep your JDK version up-to-date in any container images that you build yourself.|
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 CI 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 CI 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).