CloudBees Jenkins Enterprise 1.x administration guide
CloudBees Jenkins Enterprise 1.x administration guide
- Getting started
- Key Capabilities
- Offering CD as a Service
- Centrally secure the cluster
- Ensure cluster availability, stability, and compliance
- Pipeline for CloudBees Jenkins Enterprise
- New User Experience
- Notification Webhook HTTP Endpoints
- Cross Team Collaboration
- Expert support
- Reference architecture and materials
|CloudBees will no longer be supporting CloudBees Jenkins Enterprise 1.x after July 30, 2020. This end-of-life announcement allows CloudBees to focus on driving new technology and product innovation for CloudBees Core. For information on moving to CloudBees Core, please refer to Migrating from CloudBees Jenkins Enterprise 1.x to CloudBees Core on modern cloud platforms which has been created to help you with the migration process. Existing customers can also contact their CSM to help ensure a smooth transition.|
CloudBees Jenkins Enterprise 1.x provides Operations Center and Managed Masters as a service on most public and private cloud providers - including Amazon Web Services (AWS). CloudBees Jenkins Enterprise provides enterprise-grade features and capabilities which help organizations scale continuous integration and delivery (CI/CD).
Entrust your enterprise DevOps initiative to the only cloud native Distributed Pipeline Architecture for limitless scale and expansion. On-demand provisioning enables teams to start new projects in minutes. Enterprise features enable administrators to centrally manage teams and securely share best practices.
CloudBees Jenkins Enterprise includes verified integrations and worry-free upgrades with the CloudBees Assurance Program.
This guide assumes the administrators and organization have completed an initial technical engagement with CloudBees experts to install and perform basic configurations to the CloudBees Jenkins Enterprise cluster. This guide is meant to enable administrators interested in customizing some configurations, scaling their cluster, on-boarding new teams, or simply learning more about CloudBees Jenkins Enterprise’s architecture.
This guide covers the following key use-cases for CloudBees Jenkins Enterprise:
Offering CD as a Service to internal teams with Managed Masters and templatized agents
Centrally securing the cluster with Operations Center and Role-based Access Control
Ensuring cluster availability, stability, and compliance with the CloudBees Assurance Program, Managed Masters, and Cluster Operations
Elastically scaling the cluster with CloudBees Jenkins Enterprise’s workers and controllers
The new intuitive user experience, which guides teams with best practices on building software pipelines
Empower teams to focus on delivering value, not maintaining Jenkins, by offering Continuous Delivery as a Service to internal teams.
Isolate and enforce teams' compliance from a central dashboard. Import existing users and groups from your organization’s authentication server and assign them role-based access to resources in the CloudBees Jenkins Enterprise cluster.
CloudBees Jenkins Enterprise ensures availability with self-healing Jenkins infrastructure. Resources automatically recover and your CD pipelines automatically restart, preventing costly downtime.
Jenkins Pipeline is a suite of plugins which supports implementing and integrating continuous delivery pipelines into Jenkins as code. CloudBees Jenkins Enterprise includes all the freely available Pipeline features, plus additional plugins for enterprise environments.
CloudBees Jenkins Enterprise helps teams accelerate software delivery through seamless collaboration around the software delivery process.
The new intuitive user experience transforms how teams start their DevOps journey with a platform that guides them with best practices on building software pipelines.
The Notification Webhook HTTP Endpoint feature provides the ability to define HTTP endpoints that can receive webhook events from external services. These events are then be broadcast to listening Pipelines where they can be used to trigger builds.
The Cross Team Collaboration feature is designed to greatly improve team collaboration by connecting team pipelines to deliver software faster. It allows Pipelines to create notification events that are consumed by other Pipelines.
Receive engineer-to-engineer help and guidance from the experts at CloudBees, many of whom are CCJPE-certified and Jenkins open source committers.
Advanced administrators can deepen their expertise by reading more about how CloudBees Jenkins Enterprise works and its architecture, what its components are, and some advanced networking configurations.
Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.
CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc.
Most CloudBees products are commonly referred to by their short names—Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake—throughout various types of CloudBees product-specific documentation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about.
Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.
Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps.
While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.