CloudBees CI Lexicon

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.


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.


File created as a result of a build or Pipeline run.


A Source Control Management (SCM) term meaning a branch off the trunk of your source code with specific changes and a specific version of the code.

build agent

A computer that handles the tasks of running builds at the direction of a controller. Within the context of a CloudBees CI cluster, a build agent can be a shared resource for connected client controllers (for CloudBees CI on traditional platforms), or managed controllers, and team controllers (for CloudBees CI on modern cloud platforms).

build details

The page where a build’s logs can be explored.

build run

A single instance of a completed build.

client controller (formerly known as Client Master)

A component of CloudBees CI on traditional platforms that is configured to use CloudBees' proprietary tools and enterprise features to coordinate builds for projects.


A computing service that remotely processes and stores system resources.

cloud environment

A public, private, or hybrid computing environment that uses shared hosted resources.


A controller is a computer, VM, or container where Jenkins is installed and run. It is used to serve requests and handle build tasks.

Declarative Pipeline

A streamlined version of the Pipeline syntax that provides a smaller set of options but more powerful capabilities than the Scripted Pipeline.

downstream Pipeline

Projects triggered or executed as part of, or triggered by the results of, a Pipeline.


An executor is a computational resource for running builds and performing operations. It can run on any controller or agent. An executor can be parallelized on a specific controller or agent.


A means of organizing Projects or other items within the Jenkins workspace, much like directories in a desktop computer’s filesystem.

Freestyle project

Freestyle projects are used to implement, develop, or run simple jobs. They can span multiple operations like building and running scripts.


A folder, Pipeline, or Project in the Jenkins environment.


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 text label applied to an agent and used within a Pipeline to specify which agent should be used to execute an entire Pipeline or a Pipeline Stage.

managed controller (formerly known as Managed Master)

A component of CloudBees CI on modern cloud platforms that uses CloudBees' proprietary tools and enterprise features to coordinate builds.

multibranch Pipeline

A multibranch Pipeline can be used to automatically create Pipelines based on branches and pull requests in your repository.


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:

on-premise (on-prem)

Resources running the software are deployed in-house and within an enterprise’s IT infrastructure. An enterprise is responsible for maintaining the solution and its related processes.

operations center

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.

Pipeline stage

A discrete set of one or more Pipeline steps.

Pipeline step

A discrete Declarative Pipeline command.

Pipeline Template

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.

Pipeline Template Catalog

Pipeline Template Catalogs provide version-controlled parameterized templates for multibranch and standalone Pipeline jobs.


A process automated by Jenkins, such as testing commits to a GitHub repository or building a software package through a Pipeline.

Scripted Pipeline

The original Jenkins Pipeline syntax language, based on the Groovy scripting language. Largely supplanted by the Declarative Pipeline syntax.


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.


A single task. Fundamentally, steps tell Jenkins what to do. For example, to execute the shell command make, use the sh step: sh 'make'.

team controller (formerly known as Team Master)

A component of CloudBees CI on modern cloud platforms that uses CloudBees’ proprietary tools and enterprise features to coordinate builds.

Upstream Pipeline

A Pipeline Project that triggers or executes another Pipeline.


The location on the Jenkins controller where Jenkins builds its Projects.

Lexicon index