CloudBees Core Fundamentals

Course Objectives

• Understand the role of the CloudBees Core products in the CloudBees Suite
• Understand the differences between the CloudBees Core platforms
• Learn how to use the major CloudBees Core features that are available on all platforms

Audience

The course is applicable to:

• Administrators of CloudBees Core clusters
• Pipeline Developers
• QA Engineers
• Build and Release Engineers
• Technical Project Managers
• Architects

Prerequisites

Students should take the following courses or have CJE/CCJE certification before taking this class:

• Jenkins – Fundamentals course
• Jenkins Administration – Fundamentals course

Students should also have some familiarity with ancillary technologies related to the product:

• Docker
• Git

See Ancillary Resources for documentation and training resources for these and other related technologies.

• The class has been structured so you can do the exercises even if you are not familiar with these tools but learning them will help you implement CloudBees Core when you get home

Approach

This course includes lectures and hands-on labs

Feel free to ask questions

• Please keep on topic out of respect for all students

Each student is provided a Virtual Lab environment

• Follow along with instructor demonstrations
• Complete the hands-on labs to get real experience

Duration

This training will be delivered for one full day.

Course Modules

Description of CloudBees Core – Fundamentals course

• This is a one-day class that discusses the CloudBees Core product line and features that are included on all platforms.
• Each student has a virtual lab they can use to follow-along with the lecture materials and to do lab exercises to practice using key features.

Section 01 – CloudBees Core Overview

• Understand the CloudBees Suite of products and the place of CloudBees Core in that suite
• Understand the key differences between CloudBees Core on traditional platforms (Static Engine) and CloudBees Core on modern platforms (Cloud Engine)
• Familiarize yourself with the Operations Center through which you can coordinate and manage your CloudBees Core cluster and the CloudBees Assurance Program that helps you manage plugins and updates for your cluster

Section 02 – Single Sign-On

Learn how to integrate CloudBees Core with your SAML 2.0 identity provider to authenticate users of your cluster

Section 03 – Role-Based Access Control

Learn how to use the Role-Based Access Control feature which extends the Jenkins authorization matrix to use roles rather than just groups and users

Section 04 – Folders Plus

Understand the extended configuration capabilities of Folders Plus, which creates a private namespace for a project that provides a degree of autonomy for that project

Section 05 – Reliability Enhancements

Understand the reliability features included in CloudBees Core:

Cluster Operations

High Availability

• The implementations are quite different for CloudBees Core on modern cloud platforms (where HA is provided by default by the Kubernetes platform) and CloudBees Core on traditional platforms (where a “hot-standby” implementation of High
• Availability can optionally be configured)

Section 06 – Shared Agents and Shared Clouds

Learn how to share both static and ephemeral agents between masters and folders in the CloudBees Core cluster

Section 07 – Build Optimization

Credentials can be defined for the entire cluster, per Folder, or per Master. Understand considerations and how to implement each option

Enhanced artifact management

• Cluster-wide Copy Artifacts
• Fast Archiver (currently deprecated because of S3 issues)

Build stability and performance

• Handling aborted builds
• Restart aborted builds
• Pipeline checkpoints
• Long-running builds

Nodes Plus

Control build scheduling

• Even Load strategy
• Label throttle builds

Section 08 – Backup Enhancements

Section 09 – Best Practices

Section 10 – (Optional) — Templates

Templates are useful for standardizing builds across the organization. They are mostly useful when running Freestyle jobs; for Pipelines, shared library functions are a better solution. This section is preserved for people who are interested.