Onboarding for CloudBees CI on traditional platforms
CloudBees CI on traditional platforms is a continuous integration (CI) and continuous delivery (CD) solution that extends Jenkins. Developed for on-premise installations, CloudBees CI 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 CI on traditional platforms helps administrators manage growing installations due to ever-increasing teams, projects and jobs while getting professional support on Jenkins.
This document will help you get CloudBees CI on traditional platforms up and running.
Review this collection of recommendations to help you make decisions and ensure your environment meets the requirements before you install CloudBees CI on traditional platforms.
Before installing you will need a license (either trial or standard from CloudBees). Install the Operations Center first, then install your first Client Master. Next, configure the two to connect the Client Master to the Operations Center. The following documentation will step you through each process:
After you have completed setup, move on to configuring CloudBees CI.
One of the key features of Jenkins and CloudBees CI is extensibility through plugins, enabling it to meet the specific needs of nearly any project. With a huge variety of plugins in the Jenkins and CloudBees universe to choose from, CloudBees CI offer the CloudBees Assurance Program for users looking to simplify plugin management. CloudBees Assurance Program specifies the set of plugins, plugin versions, and plugin dependencies that are verified, compatible, or community-supported, depending on how much they have been tested. This provides greater stability and security for CloudBees CI environments.
Which plugins you install beyond the default list can be determined by many factors including your exact usage of CloudBees CI, what integrations you would like to use, and how you would like to manage the build workload.
Jenkins Pipeline is a suite of plugins which supports implementing and integrating continuous delivery pipelines into Jenkins. Pipeline provides an extensible set of tools for modeling simple-to-complex delivery pipelines "as code".
CloudBees CI’s security options follow the standard Jenkins security model, offering two axes to security, as well as options for adjusting how strict enforcement of these security settings should be. Administrators can force connected masters to delegate all of their security settings, allow teams complete control over their own security settings, or delegate only some security settings to teams.