Pipelines are a way to orchestrate the flow of the software release process. You can choose what part of your process to automate with pipelines, based on your needs. Some examples are:
From code check-in to production: After developers check in code, it is run through a pipeline that includes build, test, pre-production, and production stages, running various automation tasks in each of the stages like deploying the applications or microservices, running test automation suites, and so on, ending when the software is delivered to the production server.
From system test to production: After the software passes the system tests, it is run through a pipeline to integrate the code from multiple teams, run user acceptance tests, and deploy the software to for beta testing and then all the way to the production.
CloudBees CD/RO supports top level projects to organize related application deployment, pipeline, and release objects. These objects as well as the objects belonging to them can be in any project within CloudBees CD/RO.
Projects are top-level security containers that provide access control at the project level. All objects in a project inherit the access control settings from the project to which they belong.
Projects provide a way to logically grouping objects. If your deployment is large and has many production environments, you can organize production environments by project, with each project having its own access control settings. This makes it easier to manage and maintain multiple environments during the software delivery process.
In this section, you learn:
When you export a project while a pipeline is in progress, only the full export includes flow runtimes that have been completed. If you want to include in-progress pipeline runs in the path-to-production view and the visual indicators showing their percentage completed in the Release Dashboard, set the |
A pipeline consists of these objects:
Stages–A milestone or checkpoint in the process that consists of one or more tasks in sequential order. Running these tasks completes the milestone or checkpoint.
As each software change goes through the pipeline, it enters a stage through an entry gate only after it is approved to enter the stage. It can exit the stage through an exit gate only after it is approved to do so.
Gates–Approvals before and after a stage. A software change can enter or exit a stage only if the approval criteria at the entry or exit gate are met. Approvers are notified by email.
Tasks–Actions to be taken in a stage. They are executed in sequential order within a stage. Tasks can be defined as application or microservice processes, procedures, workflows, manual tasks and plugins to integrate with third party tools.
The following table is a reference guide to CloudBees CD/RO UI elements mentioned in this document.
In the context of pipelines, click to open stage conditions dialog.
Opens a drop down list of actions to take based on the context.
Initiates execution of an object based on the context.
Opens a popup window with useful information, content varies based on the context.
Opens the next dialog in the current sequence, the dialog varies based on the context.
Opens the edit dialog for the selected object, the dialog varies based on the context.
Located in the upper left corner, opens a top-level user menu of selections. The contents varies based on the context.
Located in the upper right corner, opens the new object dialog. Content varies by context.
Used to add a task to a pipeline stage.
Used to make a copy of a pipeline stage task.
Opens the scheduler dialog. Content varies by context.
Used to add a stage to a pipeline.
Found on individual items of an object list, usually on the right hand end of the item. Used to select the view of the selected object.
Use to group task in a pipeline stage.
Manual approval needed; the current user is on the approver’s list.
Manual approval needed; the current user is not on the approver’s list.
Located at the ends of rows in an object list. Click to expand the row to reveal more information.