catalyst-pipelines.yaml

Introduction

The catalyst-pipelines.yaml file serves as the core component for executing the pipeline, where we define its workflow. You can define the execution flow of the pipeline in this file by adding the required pipeline components using our built-in code editor or visual builder. You can check out this help page to learn more about configuring the pipeline.

Whether the pipeline is triggered manually or automatically, this file dictates the pipeline’s actions. If your pipeline is linked to a version control system, any modifications to the source code in the linked repository automatically triggers the pipeline execution, running the workflow defined in this file. Similarly, when the pipeline is triggered manually from the Catalyst console, this file is executed directly from the console interface.

Before delving into the pre-defined YAML schema definitions of Catalyst Pipelines and its usage, let’s take a moment to explore YAML in broader terms.

A YAML file is a versatile format for representing structured data across various contexts, such as configuration files, data interchange, and serialization.

The common characteristics of a YAML file include :

• YAML is not tied to any specific programming language, making it suitable for exchanging data between different systems and platforms.

• This file comprises of simple key-value pairs, lists, and maps, which can be combined and nested to represent complex data structures and configurations.

• It uses indentation to define the structure of data.

• YAML supports various data types, including scalars (strings, integers, floats, booleans, null), lists, maps (key-value pairs), and nested structures.

Catalyst Pipelines follows its own YAML schema standards, which must be strictly followed when configuring the pipeline. In the next section, we’ll delve deeper into the Catalyst YAML schema definitions.