Introduction
Advanced, Model-Based Deployment
Process-as-Code
Secure, Scalable, and Robust Architecture
Unified Object and Data Model
Architecture
CloudBees CD/RO glossary
Introduction
CloudBees CD/RO server and agent compatibility
DevOps Insight server specifications
Platform notes
Port usage
Database requirements
Disk usage
Memory settings
Checksum utility
Software licenses
Introduction
Cluster and storage requirements
Installation
Frequently asked questions
Configuration values
Introduction
Special-case installations
Installer options
Server topology best practices
Pre-installation checklist
Default installation directories
Installing DevOps Insight prerequisites
Graphical UI installation
Interactive Command-Line Installation
Silent unattended installation
Non-server platform UNIX agent installation
Installing remote agents
Moving the artifact repository in Linux
Moving the artifact repository in Windows
Connecting CloudBees CD/RO to a Microsoft SQL server
Installing the MySQL JDBC driver
Uninstalling CloudBees CD/RO
Signing in to Flow
General configuration
Horizontal scalability configuration
Maintenance
Upgrade roadmap for traditional platforms
Upgrading a non-clustered environment
Upgrading a clustered environment
Choosing the correct upgrade method
Upgrading remote agents
Upgrading the DevOps Insight server
Configuration settings preserved after an upgrade
Introduction to CloudBees CD/RO
Deploy UI Elements
Deployment Automation
Deployment Examples
Deploying Applications in Dynamic Environments
Pipeline concepts
Authoring and running pipelines
Pipeline examples
Release Management
Data Retention
Change tracking
Self-Service Catalogs
Notifications
Introduction
Understanding the DevOps Insight data model
Creating a report
Managing dashboards
Elasticsearch basics
Extending the data model
Dashboard reference
Configuring the DevOps Insight server
Introduction
Credentials and user impersonation
Credential management
Using credentials
Impersonation concepts
Use Case: using credentials in deployment automation
Cross-site request forgery protection
Bundled plugin report
Introduction to plugins
Plugin concepts
Plugin development framework
Using the pdk tool
Perl APIs
Groovy APIs
REST plugin concepts
Reporting concepts
Perl tutorials
Groovy tutorials
Known issues
Release notes
Introduction
CloudBees CD/RO server is unresponsive and displays an outofmemory error
Windows PHP does not handle time zones correctly
CloudBees CD/RO self-signed server certificate fails security scan
The AES passkey was accidentally overwritten
CloudBees CD/RO CA or intermediate CA certificate expires
Linux upgrade breaks symbolic links
Built-In database schema on disk is older than required by CloudBees CD/RO server for upgrade
Introduction
Build-test automation
Getting started
Automation platform setup
Automation platform objects
Properties
Tutorials
Using special characters in object names
Access control
Artifact management
Database configuration
Defect tracking
Email configurations and notifiers
Event log
Home page
Jobs
Licenses
Plugin manager
Procedures, steps, and parameters
Projects, schedules, and credentials
Properties
Reports
Resources and pools
Search
Server
Source control
Users and groups
Workflows
Workspaces
Support policies
Supported platforms
Third-party libraries
CloudBees subscription and services agreement
Feature definitions

Cluster and storage requirements

  • Kubernetes cluster and Helm: see Kubernetes cluster requirements.

  • Database instance

    • For a production environment installation, see Database instance for details.

    • For a non-production environment installation, the CloudBees CD/RO Helm chart automatically installs a MariaDB database instance as a built-in database.

Non-production environment

Cluster capacity

The table below specifies the default memory and CPU requested for each CloudBees CD/RO component in a non-production environment.

CloudBees CD/RO component/service CPU Memory

CloudBees CD/RO Server

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

Per replica: 6 GiB (Memory assigned to CloudBees CD/RO JVM: 4 GiB)

Web Server

0.25 CPU

256 MiB

DevOps Insight Server

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

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/RO Agent (Bound)

0.25 CPU

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

Storage

Consult the table below for default storage requirements for a non-production environment.

CloudBees CD/RO component/service Storage type Storage amount

CloudBees CD/RO Server

ReadWriteOnce

5 GiB

DevOps Insight Server

ReadWriteOnce

10 GiB

Repository Server

ReadWriteOnce

10 GiB

Production environment

Cluster capacity

For current cluster capaccity and sizing specifications, see Kubernetes cluster requirements.

Separate database instance

You must configure a separate database for your installation of CloudBees CD/RO before you initiate the installation. For current database server and sizing specifications, see Database server specifications.

Database configuration

The database can be installed inside or outside the cluster. Update the database section in the cloudbees-cd-defaults.yaml file that is specified when installing the cloudbees-flow chart. See the Database Values section in Configuration values.

Persistent Storage

CloudBees CD/RO components need varying levels of persistent storage.

  • Non-shared storage: A disk or file system that cannot be shared between two pods or two nodes. Examples include AWS EBS, GCP Persistent Disk, and Azure Disk.

  • Shared storage: A disk or file system that can be shared between two pods or two nodes. Examples include AWS EFS, GCP NFS Server, and Azure Filestore.

Consult the table below for storage requirements.

CloudBees CD/RO component/service Storage type Storage amount Mount point

Shared storage

CloudBees CD/RO Server

CloudBees CD/RO Agent (bound)

ReadWriteMany

5 GiB

/plugin-data

Repository Server

ReadWriteMany

20 GiB

/repository-data

Non-shared storage

DevOps Insight Server

ReadWriteOnce

Per replica: 4, 10 GiB Default number of replicas: 3

/elasticsearch-data

CloudBees CD/RO Agent (worker)

ReadWriteMany

5GiB

/workspace

Zookeeper

/var/lib/zookeeper

CloudBees CD/RO server persistent volume provisioning

Update the storage section in the cloudbees-cd-defaults.yaml file specified when installing the cloudbees-flow chart. See Storage values for details.

CloudBees CD/RO agent persistent volume provisioning

Update the storage section in the cloudbees-cd-agent-defaults.yaml file specified when installing the cloudbees-flow-agent chart. See Storage values for details.

Creating persistent shared storage

Create persistent shared storage on Google Cloud Platform or Amazon EKS. To get started, clone the cloudbees-example repo and then use the follow instructions.

  • Google Cloud Platform: Use Filestore to create a fully-managed NFS file server on Google Cloud.

    Find information and scripts to provision a Google Cloud Filestore instance in the cloudbees-examples repo.

  • Amazon EKI: Use Amazon Elastic File System (EFS) to create fully-managed persistent storage.

    Find information and scripts to provision an EFS instance in the cloudbees-examples repo.

Introduction
Installation