CloudBees Jenkins Solutions 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 CloudBees Jenkins Team and CloudBees Jenkins Enterprise.
This guide covers using CloudBees Jenkins Team and CloudBees Jenkins Enterprise, and is primarily intended for users of these tools rather than administrators. Administration guides can be found on this page.
If your CloudBees Jenkins Team or CloudBees Jenkins Enterprise instance has not yet been properly configured, please contact the administrator responsible to complete installation and setup.
To start implementing continuous delivery pipelines with CloudBees Jenkins Solutions, continue on to Automating projects.
Using Jenkins as a foundation, CloudBees Jenkins Solutions inherits 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 wiill 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 for CloudBees Jenkins Solutions.
Starting with the home page, a few notable sections to consider:
New Item: Clicking the "New Item" link will allow the creation of new Pipelines, Projects, or Folders
Open Blue Ocean: Clicking the "Open Blue Ocean" button will switch to the new Blue Ocean user experience available in the instance.
Agents/Executors: The "Build Executor Status" section will show currently executing Pipelines and Jobs, as well as all connected Agents.
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.
The same instance, viewed with Blue Ocean, only displays Pipelines and Projects, along with user-specified Favorites.
By clicking into "example-pipeline", the current and previously completed Runs will be displayed.
Online version published by CloudBees, Inc.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
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 book, 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 book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.