CloudBees Core on traditional platforms administration guide

CloudBees Core on traditional platforms is designed to support any organization’s CI/CD needs - regardless of whether they’re a single team with simple delivery pipelines or a massive, multi-national corporation with complex A/B deployments.

CloudBees Core on traditional platforms enables administrators to offer an internally managed CD as a Service to their teams. With CloudBees Core on traditional platforms, administrators centrally manage their organization’s build cluster using Managed Masters and templates for build agents.

Agents are computers that handle the tasks of running builds in a CloudBees Core on traditional platforms cluster, and within the context of a CloudBees Core on traditional platforms cluster, they are shared resources for connected masters.

By adding capacity, administrators can support additional Managed Masters, Jenkins agents, or improve cluster performance and resiliency.

This guide assumes that administrators and organizations have completed an initial technical engagement with CloudBees experts to install and perform basic configurations to the CloudBees Core on traditional platforms cluster. This guide is meant to enable administrators interested in customizing some configurations, scaling their cluster, on-boarding new teams, or simply learning more about CloudBees Core’s architecture.

Components

CloudBees Core has two components - the Client Master and the Operations Center. The Client Master is a Jenkins master, whose main function is to coordinate the building of projects such as Pipelines.

When a CloudBees Core installation consists of two or more Client Masters, it is usually a good idea to install an Operations Center instance to manage these Client Masters. The Operations Center provides centralized management for the following key features of a Client Master:

  • Security and role-based access controls, which controls 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.

  • Agents, which can be shared amongst different Client Masters.

Operations Center also provides other management features for Client Masters.

Concepts

Traditionally, the Jenkins user interface (UI) has concentrated on build jobs as the primary top level items within Jenkins. A number of CloudBees plugins have extended the model somewhat, e.g. the Folders plugin introduced folders as a container top level item, the CloudBees update center plugin introduced hosted Jenkins update centers as a top level item.

Operations Center introduces some additional top level items. This section details the top level items and other concepts that are used in Operations Center.

Operations Center server

The Operations Center is a special type of Jenkins instance that acts as the central authority in an Operations Center cluster.

Client Master

A CloudBees Jenkins Platform Jenkins master, which can be joined to the Operations Center cluster.

Shared agent

Shared agents are special resources created on the Operations Center server that can be leased out to Client Masters on demand to provide build resources. Agents were formerly known as slaves.

Shared cloud

In addition to shared agents, cloud providers can be used to provision temporary shared agents when demand exceeds that available from the shared agents.

Folders

The folders plugin provides a key top level item used for scoping the availability of resources. For example, credentials/shared agents/shared clouds/etc defined within a folder will only be available to items within the folder or contained sub-folders.

Sub-licensing

Each standalone Client Master must have a valid license in order to use CloudBees Jenkins Platform’s features. A license for Operations Center includes the capability to generate sub-licenses for the Client Masters that form part of the Operations Center cluster.

Reference architecture and materials

Advanced administrators can deepen their expertise by reading more about how CloudBees Core works and its architecture, what its components are, and some advanced networking configurations.

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.