Architecture for CloudBees CI on traditional platforms

2 minute read

CloudBees CI on traditional platforms consists of the following components:

Table 1. Components of CloudBees CI on traditional platforms



Client Master

A type of master that uses CloudBees’ proprietary tools and enterprise features to provide enhanced functionality for coordinating builds. A Client Master is specific to CloudBees CI on traditional platforms.

Client Masters are installed manually. A CloudBees CI on traditional platforms installation may consist of one or more Client Masters.

Client Masters offer the following functionality:

  • Role-based access control with the following default roles: administer, develop, and browse

  • Sophisticated team authorization strategies with Client Masters and Folders

operations center

An instance that provides centralized management of Client Masters and a central view into a CloudBees CI cluster.

The operations center provides the following management functionality for Client Masters:

  • Security and role-based access controls, which control access to different Client Masters, as well as various Pipeline projects and jobs on each Client Master

  • Credentials typically used to access secured external resources in Pipeline projects and jobs

  • Access to shared build agents

Having Client Masters connected to the operations center is appropriate for small to medium companies running CloudBees CI on traditional platforms.

Build agent

A computer that handles the tasks of running builds, at the direction of a master. Within the context of a CloudBees CI cluster, a build agent can be a shared resource for Client Masters. A build agent can also be dedicated to a specific master.

Figure 1. Distributed build environment with CloudBees CI on traditional platforms

The simplest CloudBees CI on traditional platforms installation consists of a single Client Master instance to coordinate builds for a single project. From this Client Master, install and configure build agents. Build agents perform the project building work on separate virtual machines from the Client Master.

A newly installed Client Master is configured by default to execute the project build work the same way a build agent is. However, for maximizing the CloudBees CI on traditional platforms implementation, CloudBees recommends dedicating a Client Master for coordinating build projects and using the build agents to perform the build work on separate virtual machines.

CloudBees recommends creating a distributed build environment by installing separate Client Master and build agents. The distributed build environment maintains the security and integrity of the Client Master and maximizes the Client Master’s performance. Shared agents can also be configured to share build agents across multiple Client Masters.

As the complexity of your organization’s CI/CD requirements and build projects increases, CloudBees recommends installing additional Client Masters to your CloudBees CI environment.

CloudBees recommends adding more Client Masters for each additional build project. This prevents build speed issues on your existing Client Master/s. This also enables each Client Master to use a different set of plugins on each of the different Client Masters, making them easier to administer.

However, once your environment needs more than one Client Master, CloudBees recommends installing operations center. operations center provides a centralized view of the Client Masters in your environment.

Without operations center, these features would need to be managed individually on each Client Master.