Table of contents

Using CloudBees Jenkins Enterprise 1.x

On this page

CloudBees Jenkins Enterprise 1.x offer a stable, secure, and reliable set of tools with which continuous integration (CI) and continuous delivery (CD) can be implemented. This guide covers implementing continuous delivery pipelines and serves as a reference for navigating .

This guide covers using CloudBees Jenkins Enterprise 1.x and is primarily intended for users of these tools rather than administrators.

If your CloudBees Jenkins Enterprise 1.x instance has not yet been properly configured, please contact the administrator responsible to complete installation and setup.

home page

To start implementing continuous delivery pipelines with CloudBees Jenkins Enterprise 1.x, continue on to Automating projects.


Using Jenkins as a foundation, CloudBees Jenkins Enterprise 1.x inherit much of the same vocabulary and concepts, which makes for an easy transition for those users already familiar with Jenkins. Some of these key concepts include:

  • Pipelines and Projects

  • Runs and Builds

  • Distributing work across Agents and Executors

Broadly defined, Pipelines and Projects contain user-defined steps, typically for the purposes of building, testing, and/or deploying software. Creating a Pipeline is recommended for most continuous integration or continuous delivery (CI/CD) use cases.

When a Pipeline executes, it will use the connected Agents and Executors in order to perform the defined steps. Agents provide the ability to execute Pipelines across multiple computers and platforms. A single instance might have Linux and Windows virtual machines attached, each running an Agent. Pipelines running in such an instance would be able to execute on Linux, Windows, or both, depending on the user’s requirements.

Once a Pipeline has been executed, it will create a Run. A Pipeline Run will contain:

  • Status: Upon completion, the overall status of the Run, which may be: Success, Failure, Aborted, Unstable (meaning a test has failed).

  • Changes: If the Pipeline was "triggered" from changes in source control (SCM), Changes will contain summary of the commits.

  • Console Output: The full standard error/output from the processes executed as part of the Pipeline.

  • Pipeline Steps: Inventory of the specific "steps" executed as part of the Pipeline, with Console Output and Status information accompanying each individual step.


The web interface contains a comprehensive amount of information surrounding each of the configured Pipelines and Projects, but in short, it provides drill-down style from Folders, to Pipelines and Projects, to Runs and Builds.

While these terms are more succinctly defined in the Glossary, this section will highlight some of these key concepts in the context of the web interface.

Starting with the home page, a few notable sections to consider:

  1. New Item: Clicking the "New Item" link will allow the creation of new Pipelines, Projects, or Folders

  2. Open Blue Ocean: Clicking the "Open Blue Ocean" button will switch to the new Blue Ocean user experience available in the instance.

  3. Agents/Executors: The "Build Executor Status" section will show currently executing Pipelines and Jobs, as well as all connected Agents.

{home page
Figure 1. Annotated main dashboard for a fresh install

The above view will only really be visible for a completely fresh installation, as Pipelines and Projects are created via the New Item link, the home page for the instance will change to include all the top-level Folders, Pipelines, and Projects.

For example, in the screenshot below, a single Folder, Multibranch Pipeline, and Pipeline are all configured.

 home page with Pipelines configured
Figure 2. Main dashbaord in the "Classic" UI

The same instance, viewed with Blue Ocean, only displays Pipelines and Projects, along with user-specified Favorites.

via Blue Ocean
Figure 3. Main dashboard in Blue Ocean

By clicking into "example-pipeline", the current and previously completed Runs will be displayed.

via the Classic UI
Figure 4. Pipeline Runs
via Blue Ocean
Figure 5. Pipeline Runs in Blue Ocean