Pipelines

Introduction

A pipeline is the highest level unit of work in the Catalyst Pipelines service. It includes a customizable sequence of stages, such as compiling code, running tests, and deploying applications, all orchestrated seamlessly to streamline your software lifecycle process.

You can create a pipeline and configure the flow of the pipeline directly from the Catalyst console. We will be discussing the detailed steps to this section in this section.

While creating the pipeline, you can choose to integrate the pipeline with an external version control system such as GitLab, GitHub or Bitbucket. This integration enables you to link a particular repository in the version control system with the pipeline, and whenever any changes are pushed to the repository, the pipeline will get triggered automatically. You can also manually trigger the pipeline from the Catalyst console, if needed. For more information on pipeline triggers, you can refer to this section.

Catalyst pipelines orchestrate based on the YAML code specified in the catalyst-pipelines.yaml file. You can refer to this page to understand the YAML schema definitions for Catalyst Pipelines and tailor the pipeline according to your specific needs. This YAML file is executed directly from the console for manual triggers or directly from the external version control system in the case of automatic triggers.

You can also implement the manual pipeline trigger and fetch the details of an existing pipeline within your application code using our Pipelines SDK package available in Java, Node.js and Python.

To define the execution flow of the pipeline in the YAML file, you have two options: you can either use our built-in drag-and-drop visual builder for an intuitive approach, or you can configure the YAML code using our code editor. You can find the step-by-step instructions to configure the pipeline in this help page.

Now, let us explore the components of the pipeline, its hierarchical structure, and usage.