When new teams join an organization, or existing teams start a new project, CloudBees CI makes it easy to provision a fully managed and access controlled controller per team. In CloudBees CI, a controller is referred to as a managed controller.
Administrators can provision managed controllers from a standardized template or they can allow team leads to provision their own managed controllers "on-demand." The number of controllers a CloudBees CI environment can handle is limited only by the capacity of the cluster.
To set the default namespace for any new managed controller or team controller, navigate toon your operations center, and then set the namespace to your preferred value.
Occasionally administrators will need to connect existing controllers to a CloudBees CI cluster, such as in the case of a team requiring a controller on Windows. Existing controllers that are connected to operations center lack key benefits of managed controllers like high availability and automatic agent management. Whenever possible, administrators should use a managed controller with CloudBees CI rather than connecting an existing controller.
client controllers are monitored by operations center just as managed controllers are monitored. Administrators can see the status of all their managed controllers, team controllers, and client controllers from the operations center controllers page. client controllers can receive configuration updates from operations center with configuration snippets. client controllers can share agents hosted in the cluster, offloading the burden of agent management from teams.
client controllers do not have the high availability features of managed controllers.
Note: The existing client controller and operations center must both accept JNLP requests.
To add a client controller, log into CloudBees CI and navigate to the operations center dashboard. Click the New Item option in the left-hand menu and provide the following information:
Item name: the name of the existing client controller to connect to the cluster
Select client controller. Just as with managed controllers, client controllers offer some customization and configuration options on creation:
On-controller executors: Number of builds to execute concurrently on the client controller itself. Default setting is 2.
Email addresses: Contact information for the administrator responsible for maintaining the client controller.
Once these settings are saved, operations center will attempt to connect the client controller to the CloudBees CI cluster.
Verify that operations center and the existing client controller can communicate with each other over both HTTP and JNLP ports. Host and port to use for JNLP is advertised through HTTP headers by each Jenkins controller.
You can connect an existing client controller to operations center by giving that client controller the TLS certificate for operations center, typically through the Configure Global Security page in operations center. For more information, see How to programmatically connect a client controller to CJOC.
If you are connecting multiple client controllers to your cluster, it is a good idea to automate that task using shared configurations.
Once the client controller is connected, administrators should configure security and access controls for the controller.
To update a managed controller’s version, the administrator needs to update the version of the Docker image for the managed controller. Once this version is updated, the managed controller and its default plugins will be upgraded to the latest versions defined in the the image, while any non-default plugins will be left at their current versions.
Once the Docker image definition is updated, the CloudBees CI administrator will need to restart the instance so the managed controller can begin using its upgraded components.
When a CloudBees CI cluster serves many teams and contains many controllers, an administrator can save time and greatly reduce the overhead of upgrading those controllers by creating a repeatable task to automate this process. In CloudBees CI, this can be achieved by defining a cluster operation in operations center.
To create this task, the administrator will first need to log into operations center, then create a New Item of the type Cluster Operations. The administrator will then needs to select the managed controllers cluster operation, and will then be given a set of pre-configured upgrade patterns to choose from.
The administrator will then need to specify which controllers to target by using the filter Uses Docker Image and picking a Docker image used by their cluster’s controllers as the upgrade target for this operation. Any controllers in the cluster using the selected image will be affected by this cluster operation.
In the Steps section, the administrator should select Update Docker Image and pick the new Docker image to bulk-upgrade the targeted controllers to. Next, the administrator should add a Reprovision step to restart the targeted controllers.
Once these settings are configured, the administrator can run the cluster operation to perform a bulk upgrade of their cluster’s controllers, or schedule the operation to run at a later time.
There may be times during an upgrade or other maintenance when it is best to have Jenkins start, but launch no projects. For example, if an upgrade is being performed in multiple steps, the intermediate steps may not be fully configured to run projects successfully. The "quiet start plugin" can immediately place the Jenkins server in "quieting down" state on startup.
Enable "quiet start" by checking the box in. When the server is restarted, it will be in the "quieting down" state. An administrator can cancel that state using the regular UI.
Uncheck the box inwhen maintenance is complete. Projects will start as usual on server restart.