First, get to know the basic workings of CloudBees CI. Having this knowledge is important to help you properly set up, customize, and use CloudBees CI.
Before installing you need a license (either trial or standard from CloudBees). Install the operations center first, then install your first client controller. Next, configure the two to connect the client controller to the operations center. The following documentation will step you through each process:
After installation is complete, you’re ready for setup. Many of the setup options are one-time actions that are required prior to using CloudBees CI on traditional platforms. Some steps are optional.
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.
To help you make your list of plugins to install, search the CloudBees CI plugin directory. Refer to CloudBees plugin support policies for details on how CloudBees classifies plugins into tiers according to how much risk a given plugin may post to a given installation’s stability.
Deliver continuously with Pipelines
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 controllers to delegate all of their security settings, allow teams complete control over their own security settings, or delegate only some security settings to teams.