Automation Platform Tasks

CloudBees CD server and agent requirements

4 minute read

Refer to the following sections for required and recommended:

Not all combinations of server version and agent version are supported. This is because of an ectool/Perl API communication incompatibility as well as a Diffie-Hellman key size incompatibility.

CloudBees CD server requirements on Kubernetes

CloudBees recommends the following guidelines for servers in a Kubernetes installation, based on deployment size.

The following guidelines are a recommended starting point. You may need to scale up, based on your environment and needs.
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 Server hardware specifications

Processor (CPU) per instance:

2 CPU’s

Default number of replicas: 1

Processor (CPU) per instance:

4 CPU’s

Default number of replicas: 3

Processor (CPU) per instance:

16 CPU’s

Default number of replicas: 3

Processor (CPU) per instance:

4 core processors per instance

Available RAM per replica:

16 GB (minimum)

32 GB (recommended)

Max JVM Heap size: 85%*

Available RAM per replica:

32 GB (minimum)

64 GB (recommended)

Max JVM Heap size: 85%*

Available RAM per replica:

64 GB (minimum)

128 GB (recommended)

Max JVM Heap size: 85%*

Available RAM per replica:

8 GB (minimum)

16 GB (recommended)

Max JVM Heap size: 40%*

Local storage per replica: 20 GB

Local storage per replica: 40 GB

Local storage per replica: 60 GB

Local storage per replica: 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 or more 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 CD server requirements for traditional installations

CloudBees recommends the following guidelines for servers in a traditional installation, based on deployment size.

The following guidelines are a recommended starting point. You may need to scale up, based on your environment and needs.
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 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 CD agent requirements

These requirements are applicable to both traditional and Kubernetes installations.

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 components: 256 MiB (minimum), 512 MiB (recommended)

  • Disk Space: 5 GB

Diffie-Hellman key size requirement

To enable the CloudBees CD server versions 7.0 or newer to configure Diffie-Hellman cipher suites properly, CloudBees CD uses OpenSSL-1.0.1T or newer versions with SSLv2 enabled. Because of OpenSSL and JRE changes, the minimum Diffie-Hellman key size requirement is increased to 1024 bits (from 768 bits) as of version 7.0.

Server versions 7.0 or newer use Jetty (a Java HTTP server), which listens on the 8000 (unsecure) and 8443 (secure) ports. Server versions 7.0 or newer use Java 1.8.0_66, in which the ephemeral DH key size defaults to 1024 bits during SSL/TLS handshaking in the SunJSSE provider.

For details on the increase of the key size requirement as of Java 1.6-u101, refer to the Java 6u101 b31 release notes. For details as of Java 1.7-u85, see the Java 7u79 release notes.

Because their minimum key size is 1024 bits, agent versions 7.0 or newer can connect only to:

  • Server versions 5.4, 6.0.1, or 6.5 or higher via ectool

  • External applications that require SSL with a minimum key size of 1024 bits

However, CloudBees CD Automation Platform agents of versions 5.0.6, 5.3, or 5.4 and CloudBees CD agent versions 6.0.1 or 6.5 or newer can connect to all CloudBees CD server versions (including 7.0 or newer) via ectool and ec-perl.

CloudBees CD Automation Platform server versions 5.0.6 or 5.3 or newer can run jobs using all agent versions (including 7.0 or newer). CloudBees CD server versions 7.0 or newer can run jobs using CloudBees CD Automation Platform agent versions 5.0.6 or 5.3 or newer.