Supported platforms for CloudBees CD

When running CloudBees CD, consult this page for supported platforms.

Kubernetes

Kubernetes Pre-9.2 9.2 10.0 Preview

Amazon EKS 1.15.10

Amazon EKS 1.14.7

Amazon EKS 1.13.10

GKE 1.15.x

GKE 1.14.x

GKE 1.13.x

OpenShift 4.x

Helm Pre-9.2 9.2 10.0 Preview

Helm 3, version 3.1.0 or later

Helm 2, version 2.14 or later

Helm 2, version 2.12 or later

  • CloudBees supports only production releases of Helm: RC, beta, patch or experimental releases of Helm are not supported.

  • If you are using Helm 2 to manage your application deployment: Tiller server production release version 2.x, starting with version 2.12, must be installed on your Kubernetes cluster.

Traditional platforms

Supported platform information for CloudBees CD servers and agents is below. Consult platform notes for additional implementation information about these platforms.

Server platforms

Supported platforms for the CloudBees CD, web, repository, and DevOps Insight servers.

Microsoft Windows platforms 8.0 8.4 8.5 9.0 9.1 9.2 10.0 Preview

Windows 10 (64-bit)

Windows 8.1 (64-bit)

Windows 7 (64-bit)

Windows Server 2016 (64-bit)

Windows Server 2012 R2 (64-bit)

Windows Server 2012 (64-bit)

Windows Server 2008 R2 (64-bit)

Linux platforms 8.0 8.4 8.5 9.0 9.1 9.2 10.0 Preview

CentOS 7 (64-bit)

Red Hat Enterprise Linux 8 (64-bit)

Red Hat Enterprise Linux 7 (64-bit)

Red Hat Enterprise Linux 6 (64-bit)

Red Hat Enterprise Linux 5 (64-bit)

Ubuntu 18.04 (64-bit)

Ubuntu 16.04 (64-bit)

Ubuntu 14.04 (64-bit)

Ubuntu 12.04 (64-bit)

Ubuntu 10.04 (64-bit)

Agent platforms

You can drive automation on target machines by either installing agents natively or by running them remotely using proxy agents.

Native agent platforms

Microsoft Windows platforms 8.0 8.4 8.5 9.0 9.1 9.2 10.0 Preview

Windows 10 (64-bit)

Windows 8.1 (64-bit)

Windows 7 (64-bit)

Windows Server 2019 (64-bit)

Windows Server 2016 (64-bit)

Windows Server 2012 R2 (64-bit)

Windows Server 2012 (64-bit)

Windows Server 2008 R2 (64-bit)

Windows Server 2008 (64-bit)

Linux platforms 8.0 8.4 8.5 9.0 9.1 9.2 10.0 Preview

CentOS 7 (64-bit)

Red Hat Enterprise Linux 8 (64-bit)

Red Hat Enterprise Linux 7 (64-bit)

Red Hat Enterprise Linux 6 (64-bit)

Red Hat Enterprise Linux 5 (64-bit)

Ubuntu 18.04 (64-bit)

Ubuntu 16.04 (64-bit)

Ubuntu 14.04 (64-bit)

Ubuntu 12.04 (64-bit)

Ubuntu 10.04 (64-bit)

SUSE Linux Enterprise Server 12.3 (32- and 64-bit)

SUSE Linux Enterprise Server 12.1 (32- and 64-bit)

SUSE Linux Enterprise Server 11.4 (32- and 64-bit)

SUSE Linux Enterprise Server 10.4 (32- and 64-bit)

SUSE Linux Enterprise Server 10.3 (32- and 64-bit)

Other platforms 8.0 8.4 8.5 9.0 9.1 9.2 10.0 Preview

AIX 7.1

HP-UX 11i v1 (11.11) or later (PA-RISC 2.0 architecture)

macOS X 10.15 Catalina, 64-bit (Intel architecture)

macOS X 10.4 Tiger, 32-bit only (Intel architecture)

Oracle Solaris 10 (SPARC and Intel x86 architectures)

Oracle Solaris 9 (SPARC architecture)

Proxy agents for other platforms

A proxy agent is a CloudBees CD agent that channels to a proxy target, which lets you drive automation in an agentless fashion. A proxy agent is an agent on a supported Microsoft Windows or Linux platform that you use to take actions on any platform that is not listed above. For example, you can use a proxy agent to automate actions on an IBM z Systems mainframe running z/OS or Linux OS.

You can use a proxy agent to communicate with any target platform that can run commands via an SSH protocol.

Hardware requirements

Small to mid-range deployments Large deployments Very large deployments
  • <1K jobs per day

  • <100 running pipelines per day

  • < 50K job steps

  • ~ 10K jobs per day

  • ~ 200 running pipelines per day

  • ~ 500K job steps per day

  • ~ 100K jobs per day

  • ~ 2000 running pipelines per day

  • ~ 5M job steps per day

CloudBees CD Server Hardware Specifications

Processor (CPU) per instance:

4 core processor

Processor (CPU) per instance:

8 core processor per instance

Processor (CPU) per instance:

16 core processor per instance

Available RAM per instance:

16 GB (minimum)

64 GB (recommended)

Max JVM Heap size: 40%*

Available RAM per instance:

64 GB (minimum)

128 GB (recommended)

Max JVM Heap size: 40%*

Available RAM per instance:

64 GB (minimum)

256 GB (recommended)

Max JVM Heap size: 70%*

Disk Space: 20 GB

Disk Space: 30 GB or more

Disk Space: 50 GB or more

Instances in cluster:

1 (non-clustered)

2-3 (recommended for HA)

Instances in cluster:

3 instances

Instances in cluster:

3-4 instances

CloudBees CD Agent Hardware Specifications

  • Processor (CPU) per instance: 1 CPU processor from set of cores

  • JVM heap size per stand-alone agent: 16 MiB (minimum), 64 MiB (recommended)

  • JVM heap size when shared with other CloudBees CD components: 256 MiB (minimum), 512 MiB (recommended)

  • Disk Space: 5 GB

Database server requirements

Small to mid-range deployments Large deployments Very large deployments
  • <1K jobs per day

  • <10 pipeline runs per day

  • < 50K job steps

  • ~ 10K jobs per day

  • ~ 20 pipeline runs per day

  • ~ 500K job steps per day

  • ~ 100K jobs per day

  • ~ 200 pipeline runs per day

  • ~ 5M job steps per day

Recommended database:

Any supported database type - Mysql, MS SQL Server, Oracle

Recommended database:

Oracle or MS SQL Server

Recommended database:

Oracle or MS SQL Server

Processor (CPU): 4 core processor

Processor (CPU): 8 core processor

Processor (CPU): 16 core processor

Available RAM: 16 GB

Available RAM: 20 GB or more

Available RAM: 20 GB or more

Supported databases

Platform 8.0 8.4 8.5 9.0 9.1 9.2 10.0 Preview

MySQL 5.7 or later 1

MySQL 5.6 1

MySQL 5.5.12 1

MS SQL Server 2017

MS SQL Server 2016

MS SQL Server 2014

2

2

2

MS SQL Server 2012 R4

2

2

2

MS SQL Server 2008, 2008 R2

Oracle 19c

Oracle 18c

Oracle 12c

Oracle 11g Release 2

1 Clean installations of the CloudBees CD server require the MySQL JDBC driver. For upgrades, additions to my.cnf/my.ini are required. See Installing the MySQL JDBC Driver.

2 As of version 9.2, CloudBees Flow has ended support for HTTPS connection types older than TLS 1.2. If you are using MS SQL Server 2012 or 2014, you must update it to support TLS1.2. For details, see the Microsoft TLS 1.2 support for Microsoft SQL Server web page.

DevOps Insight server requirements

Small to mid-range deployments Large deployments Very large deployments
  • <1K jobs per day

  • <10 pipeline runs per day

  • < 50K job steps

  • ~ 10K jobs per day

  • ~ 20 pipeline runs per day

  • ~ 500K job steps per day

  • ~ 100K jobs per day

  • ~ 200 pipeline runs per day

  • ~ 5M job steps per day

Processor (CPU) per instance:

4 core processor

Processor (CPU) per instance:

4 core processor

Processor (CPU) per instance:

8 core processor

Available RAM per instance:

4 GB (minimum)

8 GB (recommended)

JVM Heap size for Elasticsearch:

2 GB (minimum)

4 GB (recommended)

JVM Heap size for Logstash:

1 GB (minimum)

2 GB (recommended)

Available RAM per instance:

8 GB (minimum)

16 GB (recommended)

JVM Heap size for Elasticsearch:

4 GB (minimum)

8 GB (recommended)

JVM Heap size for Logstash:

2 GB (minimum)

4 GB (recommended)

Available RAM per instance:

8 GB (minimum)

16 GB (recommended)

JVM Heap size for Elasticsearch:

4 GB (minimum)

8 GB (recommended)

JVM Heap size for Logstash:

2 GB (minimum)

4 GB (recommended)

Disk Space: 5 GB

Disk Space: 10 GB

Disk Space: 20 GB

Instances in cluster:

1 (non-clustered)

2-3 (recommended for HA)

Instances in cluster:

3 instances

Instances in cluster:

3 or more instances

*The maximum JVM heap size specified in wrapper.conf, expressed in percentage of total available memory.

Kubernetes cluster requirements

The table below specifies the default memory and CPU requested for each CloudBees CD component in the production environment.

CloudBees CD component/service CPU Memory

CloudBees CD Server

Per replica: 2 CPU, Default number of replicas: 1

Per replica (minimum): 8 GiB (Memory assigned to CloudBees CD JVM: 6 GiB)

Per replica (recommended): 32 GiB (Memory assigned to CloudBees CD JVM: 30 GiB)

Local storage per replica: 20 GB

Web Server

0.25 CPU

256 MiB

DevOps Insight Server

Per replica: 0.1 CPU, Default number of replicas: 3

Per replica: 2 GiB (Memory assigned to Elasticsearch JVM: 1 GiB)

Repository Server

0.25 CPU

512 MiB (Memory assigned to Repository JVM: 512 MiB)

CloudBees CD Agent (Bound)

0.25 CPU

512 MiB (Memory assigned to Agent JVM: 256 MiB)

CloudBees CD Agent (Worker)

0.25 CPU

512 MiB (Memory assigned to Agent JVM: 64 MiB)

ZooKeeper

Per replica: 0.25 CPU, Default number of replicas: 3

Per replica: 512 MiB

Browser requirements

CloudBees CD supports the following web browsers:

  • Microsoft Internet Explorer 11

  • Microsoft Edge

  • Mozilla Firefox

  • Google Chrome

Web browser extensions such as AdBlock Plus for Google Chrome can interfere with the display of CloudBees CD web pages. You should disable any ad-blocking browser extensions or add an exclusion for CloudBees CD web pages.

DevOps Foresight server platforms

DevOps Foresight has been tested on these platforms:

  • Windows Server 2008

  • Ubuntu v18.04