3 minute read

CloudBees Release Orchestration SaaS platform allows you to create Pipelines to 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. When a step is successfully executed, it moves to the next step. When a step fails to execute, the Pipeline fails to complete the execution. The successful execution of a pipeline happens when all the steps defined in the pipeline executes successfully.

You can create CI/CD pipelines with the configured DevOps and IT Ops tools. You can also use CloudBees Release Orchestration SaaS’s unique drag and drop feature. You can create your pipeline by dragging and dropping your tools to take your code check in, build, test, deploy, all the way to production. You can create a pipeline, save it as a draft, enable the pipeline for execution, and delete a pipeline. The platform allows you to create multiple CI pipelines merged into one CD pipeline.

You must define the following configurations to create a new pipeline:

  • Create a New Pipeline

  • Source Control Configuration

  • Builder Configuration

  • Deployer (CI Tool) Configuration

  • Auto/Manual Test Configuration

  • Approval Configuration

  • Custom Script/Test Configuration

  • Pipeline Connector

  • External Pipelines On the Pipelines page, on the left pane, you can view the following:

  • Pipelines: Displays all the pipelines you have created and on the right you can view the configuration of all the tools to create pipelines as groups with product, team and component format.

  • Templates: Displays all the templates defined to easily create a pipeline

  • New Pipeline: Allows you to create a new pipeline and save it in the platform

  • Enabled Pipelines: .Displays the pipelines that are published and have started execution in On-premise. You cannot edit an enabled pipeline

  • Disabled Pipelines: Displays the pipelines that are disabled. You can disable any pipeline if you do not want the specific pipeline to run. The pipeline is still available in the platform but the platform does not listen to any of the commits

  • Draft Pipelines: Displays the pipelines that are defined and saved in draft mode. The pipeline is defined but saved in the Cloud database. You can click and continue defining the pipeline

  • Retired Pipelines: Displays the pipelines that are deleted. The pipelines are not removed from the platform but they are saved as retired pipelines. The platform does not listen to any commits from this pipeline

  • Delete a pipeline configuration: On the Pipeline screen, you can drag and drop your DevOps and SDLC tools to define your pipeline. When you drag and drop each tool into the screen, the platform allows you to edit or delete each configuration, by a single click at the top right corner of each tool step CloudBees Release Orchestration SaaS also allows you to create pipeline with Pipeline as Code.Pipeline as code is a practice of defining pipelines through source code which can stored in repository such as GitHub to manage changes. CloudBees Release Orchestration SaaS provides this feature to allow Users to define pipelines in YAML format and stored in a GitHub repository to synchronize the creation & updates to pipelines in Pipeline composer.

Alternatively, Pipeline Composer has YAML editor to allow User to define pipelines without the need for a Git repository. However, all pipelines synchronized from GitHub are displayed in YAML editor in Read-only mode only.

By clicking on Code radio button allows you to use Pipeline as code feature.