Supported platforms for CloudBees CD/RO on traditional platforms

5 minute read

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

Looking for information about CloudBees CD/RO on Kubernetes platforms? Refer to Supported platforms for CloudBees CD on Kubernetes.

Server platforms

Supported platforms for the CloudBees CD/RO, web, repository, and CloudBees Analytics servers.

Microsoft Windows platforms9.09.19.210.010.110.210.3

Windows 10 (64-bit)

Windows 8.1 (64-bit)

Windows 7 (64-bit)

Windows Server 2016 (64-bit)

Windows Server 2012 R2 (64-bit)

Linux platforms9.09.19.210.010.110.210.3

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 20.04 (64-bit)

Ubuntu 18.04 (64-bit)

Ubuntu 16.04 (64-bit)

Ubuntu 14.04 (64-bit)

Agent platforms

Not applicable for CloudBees Analytics for CloudBees CI installations.

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 platforms9.09.19.210.010.110.210.3

Windows 10 (64-bit)

1

Windows 8.1 (64-bit)

1

Windows Server 2019 (64-bit)

Windows Server 2016 (64-bit)

Windows Server 2012 R2 (64-bit)

Windows Server 2012 (64-bit)

1 Images not available on GCP.

Linux platforms9.09.19.210.010.110.210.3

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)

Ubuntu 20.04 (64-bit)

Ubuntu 18.04 (64-bit)

Ubuntu 16.04 (64-bit)

Ubuntu 14.04 (64-bit)

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

Other platforms9.09.19.210.010.110.210.3

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

Not applicable for CloudBees Analytics for CloudBees CI installations.

A proxy agent is a CloudBees CD/RO 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.

Supported databases

Platform9.09.19.210.010.110.210.3

MySQL 8.0 1

MySQL 5.7 or later 1

MS SQL Server 2019

MS SQL Server 2017

MS SQL Server 2016

MS SQL Server 2014

2

2

2

2

2

MS SQL Server 2012 R4

2

2

2

2

2

Oracle 19c

Oracle 18c

Oracle 12c

MariaDB 3

1 Clean installations of the CloudBees CD/RO 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.

3 The built-in MariaDB database is a supported database for production use with CloudBees Analytics for CloudBees CI, only. It continues to not be supported for production use for CloudBees CD/RO and full CloudBees Software Delivery Automation.

Supported browsers

CloudBees CD/RO 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/RO web pages. You should disable any ad-blocking browser extensions or add an exclusion for CloudBees CD/RO web pages.

CloudBees CD/RO server requirements for traditional installations

Small to mid-range deploymentsLarge deploymentsVery large deploymentsCloudBees Analytics for CloudBees CI
  • <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

Not applicable.

CloudBees CD/RO 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

Processor (CPU) per instance:

4 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: 60%*

Available RAM per instance:

64 GB (minimum)

256 GB (recommended)

Max JVM Heap size: 70%*

Available RAM per instance:

8 GB (minimum)

16 GB (recommended)

Max JVM Heap size: 40%*

Disk Space: 20 GB

Disk Space: 30 GB or more

Disk Space: 50 GB or more

Disk Space: 10-20 GB (learn more here)

Instances in cluster:

1 for non-clustered

2-3 recommended for HA

Instances in cluster:

3 instances

Instances in cluster:

3-4 instances

Instances in cluster:

1 for non-clustered

3 recommended for HA (MariaDB is not supported in a clustered deployment.)

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

CloudBees Analytics server requirements

Small to mid-range deploymentsLarge deploymentsVery large deploymentsCloudBees Analytics for CloudBees CI
  • <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

  • ~ 100 builds per day

  • 200 controllers

Processor (CPU) per instance:

4 core processor

Processor (CPU) per instance:

4 core processor

Processor (CPU) per instance:

8 core processor

Processor (CPU) per instance:

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

Available RAM per instance:

3 GB (minimum)

JVM Heap size for Elasticsearch:

1 GB (minimum)

JVM Heap size for Logstash:

512 GB (minimum)

Disk Space: 5 GB

Disk Space: 10 GB

Disk Space: 20 GB

Disk Space: 10 GB

Instances in cluster:

1 (non-clustered)

2-3 (recommended for HA)

Instances in cluster:

3 instances

Instances in cluster:

3 or more instances

Instances in cluster:

1 (non-clustered)

3 (recommended for HA)

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

Database server requirements

Applicable to both traditional and Kubernetes installations

Small to mid-range deploymentsLarge deploymentsVery 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

CloudBees CD/RO Agent requirements

Not applicable for CloudBees Analytics for CloudBees CI installations.
  • 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/RO components: 256 MiB (minimum), 512 MiB (recommended)

  • Disk Space: 5 GB