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.
CloudBees Assurance Program xref:account-management:ROOT:sso-saml-setup.adoc
Before jumping to the implementation, you should understand the infrastructure and skills needed to install, onboard users, and set up. You can take a look at this CloudBees CI on modern cloud platforms planning guide for some important topics to consider before installation, such as verifying you are using a supported Kubernetes version, that you can have access to a namespace in Kubernetes, and other items.
Use the Requirements validation tool to determine if your Kubernetes cluster meets the known requirements for CloudBees CI on modern cloud platforms.
Use installation instructions that are tailored to the Kubernetes management platform that you’re using. Follow the Generic Kubernetes instructions if you installed Kubernetes manually or are using a platform that is not listed below.
The following videos show how to install and begin the initial setup of CloudBees CI on modern cloud platforms. The installation video shows you how to use the CloudBees CI Helm chart with HTTPS support and NGINX Ingress Controller, if you don’t have it already. Even though the video series focuses on GKE, it is a good resource for other cloud providers as it provides a set of tasks that are not specific to a certain Kubernetes provider.
After installation is complete, you’re ready for setup.
Setup options vary depending on your environment, but the following options are commonly used:
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.
The following options are available to help you to maintain CloudBees CI on modern cloud platforms: