This lexicon is a collection of terms and definitions used by CloudBees.
An agent is typically a machine, or container, which connects to a Jenkins controller and executes tasks when directed by the controller. An agent can be configured to have multiple executors, meaning it can run multiple tasks at a time from one or more controllers. In CloudBees CI, an agent can be a shared resource available to multiple controllers or it can be dedicated to a single controller.
A network configuration that prevents network-connected resources, such as computers or processes, to behave as if they are physically isolated from unsecured networks, such as the public internet or an unsecured local area network.
The user interface that administrators can use to manage plugin versions and enforce compliance with the CloudBees Assurance Program’s recommended sets of plugins and versions. It provides a centralized view of the monitored plugins, recommended actions, and configuration options.
A step that can be added to a Pipeline that allows you to restart a Pipeline build from a certain point. A new flow build, using a new build number, is started. It skips all of the steps preceding the checkpoint and runs only the remainder of the flow.
CloudBees CI is a fully-featured, cloud native capability that can be hosted on-premise or in the public cloud to deliver CI at scale. It provides a shared, centrally managed, self-service experience for all your development teams running Jenkins. CloudBees CI on modern cloud platforms is designed to run on Kubernetes. CloudBees CI on traditional platforms has been developed for on-premise installations.
The new single source of truth to monitor and optimize the underlying CI infrastructure across your enterprise. With actionable insights, you can enhance your build performance, right-size your workloads over demand cycles, prevent unplanned downtimes, get a holistic view of your plugin usage across all your Pipeline jobs, and more.
A program that is designed and maintained by CloudBees to test plugins, plugin versions, and plugin dependencies to determine their stability. Verified plugins in the CAP are both independently stable and tested as a whole to ensure compatibility with each other and the CloudBees CI instance. This provides greater stability and security for CloudBees CI environments.
A method of simplifying the configuration of the operations center or controller by capturing the configuration of the operations center or controller in human-readable declarative files that can be used in a reproducible way.
Jenkins® is an open source automation server. With Jenkins, organizations can accelerate the software development process by automating it. Jenkins manages and controls software delivery processes throughout the entire lifecycle, including build, document, test, package, stage, deployment, static code analysis and much more.
A node is an operating system or container running Jenkins as an agent. Most work a Pipeline performs is done in the context of one or more declared node steps. Confining the work inside of a node step does two things:
A component of CloudBees CI that enables centralized management of managed controllers and team controllers (for CloudBees CI on modern cloud platforms), and client controllers (for CloudBees CI on traditional platforms).
In CloudBees CI and CloudBees Jenkins Platform, a 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" via the Pipeline DSL.
A set of features that allow Jenkins users to define Pipeline job processes with code and are stored and versioned in a source control repository. These features allow Jenkins to discover, manage, and run jobs for multiple source control repositories and branches, eliminating the need for manual job creation and management.
Runtime validations that work for both scripted and declarative Pipelines and provide administrators a way to include warnings for or block the execution of Pipelines that do not comply with certain regulatory requirements, rules, or best practice guidelines.
CloudBees Pipeline Templates give your organization the ability to enforce consistency. A small team can determine what Pipeline options are appropriate for your needs, and all of your development teams can choose from one of those options when they set up a software delivery project.
A configuration file that specifies plugins and their associated versions. It widens the acceptable scope of plugins beyond those defined by the CloudBees Assurance Program. This scope includes the ability to specify plugin dependency rules and acceptable version ranges for these plugins.
Access control provides security for all system objects and a comprehensive mechanism to control how individuals use the system. The Role-based Access Control plugin is the preferred authorization strategy for CloudBees CI, and is installed by default. The RBAC plugin gives a CloudBees CI administrator the ability to define multiple security roles.
CloudBees Software Delivery Automation enables enterprises to optimize their software delivery process for increased innovation and security by connecting, automating, and orchestrating the tools and functions across development, operations, and shared services teams.
An option in CloudBees CI that lets you use a self-signed certificate or a custom certificate authority (CA) to access internal HTTPS services, such as a source code management (SCM) repository or an artifact repository.
A utility that is built into Jenkins that is helpful for creating bits of code for individual steps, discovering new steps provided by plugins, or experimenting with different parameters for a particular step.
A stage is a step for defining a conceptually distinct subset of the entire Pipeline, for example: "Build", "Test", and "Deploy". A stage is used by many plugins to visualize or present Jenkins Pipeline status/progress.
Enables Jenkins administrators to host their own Update Center for the Jenkins instances that they administer. This Update Center will provide the Jenkins administrator with the ability to both restrict the plugins available and host their own custom plugins.