2 minute read
On this page

CloudBees Release Orchestration SaaS pipelines help you define your release process with multiple workflows and approvals in sequential and/or parallel stages.


Pipelines are a sequence of steps that enable you to build, test, and deploy applications. You can define your steps and automate the execution of your pipelines.

You can create CI/CD pipelines in CloudBees Release Orchestration SaaS by selecting UI tools to check in code, build, test, and deploy all the way to production. CloudBees Release Orchestration SaaS enables you to create multiple CI pipelines merged into one CD pipeline.

The following table defines each option in CloudBees Release Orchestration SaaS Pipeline Composer and lists the corresponding links to more information.

Table 1. CloudBees Release Orchestration SaaS Pipeline Composer UI tools
Name and link Description

Create your own CI/CD pipelines with Pipeline Composer.

You can configure all your source control parameters.

Define your build configuration.

You can configure CI deployment.

Configure automated or manual testing to catch errors.

You can add a manual approval step before deployment or executing a new step.

A custom script is useful when you want to execute another specific step within a stage of your pipeline.

You can connect a CI pipeline with a CD pipeline in your pipeline group.

As an alternative to the UI tools in Pipeline Composer, you can define pipelines in YAML format and optionally store them in a GitHub repository.

You can group pipelines or jobs in order to track activity and performance in one place.

CloudBees Release Orchestration SaaS Agent enables you to add a pipeline outside of your group to your pipeline.

Pipeline editor
Figure 1. Pipeline Composer features highlighted

As shown in Figure 1, Pipeline Composer displays the following:

  1. Two editing modes, visual and code. In visual, you can select a series of UI tools to define your pipeline. Alternatively, you can use a code editor to define your pipeline in YAML format.

  2. Access to pipeline templates. Templates are common pipeline definitions that can be reused or modified for ease in configuration.

  3. Access to create a new pipeline.

  4. Access to manage and edit pipeline groups.

  5. A list of pipelines. In the example group, there are enabled, disabled, and draft pipelines displayed. You can select a pipeline to view its definition.