CloudBees Core on Traditional Platforms Installation Guide:

Overview

CloudBees Core on traditional platforms is a continuous integration (CI) and continuous delivery (CD) solution that extends Jenkins. Developed for on-premise installations, CloudBees Core on traditional platforms offers stable releases with monthly updates, as well as additional proprietary tools and enterprise features to enhance the manageability and security of Jenkins. CloudBees Core on traditional platforms helps administrators manage growing installations due to ever-increasing teams, projects and jobs while getting professional support on Jenkins.

As mentioned earlier, CloudBees Core on traditional platforms consists of two components - the Client Master and the Operations Center, where the Client Master is a Jenkins master, whose main function is to coordinate the building of projects such as Pipelines.

Setting up your CloudBees Core on traditional platforms installation

The simplest CloudBees Core on traditional platforms installation consists of a single Client Master instance to coordinate project builds. From this Client Master, you can install and configure agents (to perform the project building work) on other infrastructure.

The Client Master itself can also perform project building work (as an agent), which is how a newly installed Client Master is configured by default. However, to maintain the security and integrity of your Client Master and maximize its performance, it is good practice to dedicate the Client Master’s purpose to coordinating project builds only and have your agents performing the building work elsewhere. This is known as a "distributed build environment" or "distributed build architecure".

As the complexity of your organization’s CI/CD requirements and build projects begin to increase, you may need to consider installing additional Client Masters to your CloudBees Core on traditional platforms setup. This is useful when you:

  • begin to notice build speed issues on your existing Client Master/s
    and/or

  • need to install different sets of plugins on different Client Masters.

Once your CloudBees Core on traditional platforms installation consists of two or more Client Masters, it is usually a good idea to install the Operations Center. The Operations Center is useful in its ability to provide centralized management for the following key features of a Client Master:

  • 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.

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

Without an Operations Center, these features would need to be managed individually on each Client Master.

Estimating your requirements for CloudBees Core on traditional platforms

You can estimate your organization’s Client Master and executor [1] requirements, based on the number of developers in your organization. These requirements should provide a good basis for your initial CloudBees Core on traditional platforms installation.

  1. Estimate the total number of Client Master items (i.e. Pipeline projects, jobs and other items configured on a Client Master) in your CloudBees Core on traditional platforms installation. This can be based on the approximation:

    • No. of (Client Master) items = no. of developers * 3.333

  2. Using this "no. of items" value, estimate the number of Client Master instances required for your CloudBees Core on traditional platforms installation. Typically, each CPU core of the hardware on which the Client Master is installed can support a maximum of 100 Client Master items. If, for example, your Client Master’s hardware has 5 CPU cores, then the Client Master can support a total of 500 items. Assuming this hardware arrangement for each Client Master:

    • No. of Client Masters required = no. of items / 500

  3. Last, you can estimate the number of executors based on this simple formula/approximation:

    • No. of executors = no. of items * 0.03

Your estimated required number of Client Masters (step 2 above) can help you plan how many Client Masters you should install for your initial CloudBees Core on traditional platforms installation. If your estimate is two or more Client Masters, then consider installing a Operations Center to manage these Client Masters.

Note
There is no need to install a Operations Center server if you only require a single Client Master instance.

1. An executor is a slot of execution of build work defined by a Pipeline project/job, typically performed on an agent.