# Pipeline Overview

Pipelines in Flosum allow you to automate the process of moving changes between environments. A pipeline connects a source branch to one or more target orgs and defines the execution steps for validation, testing, and deployment.

The Pipelines page provides a searchable list of all available pipelines along with their metadata, making it easy to track activity and manage automation.

![](https://docs.revvy.io/~gitbook/image?url=https%3A%2F%2F599358484-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FlcWbuZareqS9jci4Vs22%252Fuploads%252F8SJ35MAqiIz15H5XjxBz%252Fimage.png%3Falt%3Dmedia%26token%3D834f6e12-6e24-4150-bcd5-687f34d6e4fd\&width=768\&dpr=4\&quality=100\&sign=7c66d49b\&sv=2)

#### Pipelines List View <a href="#pipelines-list-view" id="pipelines-list-view"></a>

When viewing the **Pipelines** tab, the following details are displayed:

* **Pipeline Name** – The configured name of the pipeline.
* **Created By** – The user who created the pipeline.
* **Last Activity** – Timestamp of the last execution or update.
* **Branch** – The source branch associated with the pipeline.
* **Orgs** – The number of orgs connected to the pipeline.
* **Actions** (⋮) – Delete a pipeline name or edit pipeline name.

**Filters**

* **Search** – Find pipelines by name.
* **Branches** – Filter by associated branches.
* **Latest Activity** – Sort pipelines by most recent or oldest activity.

#### Creating a Pipeline <a href="#creating-a-pipeline" id="creating-a-pipeline"></a>

![](https://docs.revvy.io/~gitbook/image?url=https%3A%2F%2F599358484-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FlcWbuZareqS9jci4Vs22%252Fuploads%252FS1iUjoeWlkMe1AQ1unIW%252Fimage.png%3Falt%3Dmedia%26token%3Df7ef4070-62f5-4666-a940-b2333685482c\&width=768\&dpr=4\&quality=100\&sign=3b522ff1\&sv=2)

To create a new pipeline:

1. Navigate to the **Pipelines** tab.
2. Click + **Create pipeline.**
3. In the **Add pipeline** modal, enter a name for the pipeline.
4. Click **Create pipeline** to save.

The new pipeline will appear in the list and can be further configured with branches and orgs.

#### Deleting a Pipeline <a href="#deleting-a-pipeline" id="deleting-a-pipeline"></a>

![](https://docs.revvy.io/~gitbook/image?url=https%3A%2F%2F599358484-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FlcWbuZareqS9jci4Vs22%252Fuploads%252FQ0JHIyzly9egUO1OKC1S%252Fimage.png%3Falt%3Dmedia%26token%3D3d85af60-0076-459a-916c-c1afa0c96e2b\&width=768\&dpr=4\&quality=100\&sign=6d59e4cb\&sv=2)

To delete an existing pipeline:

1. Navigate to the **Pipelines** tab.
2. Locate the pipeline you want to delete.
3. Click the ⋮ **(More actions)** menu next to the pipeline.
4. Select **Delete**.
5. Confirm the deletion in the dialog box.

⚠️ Note: Deleting a pipeline permanently removes it from the list. Ensure it is no longer needed before deleting. ➡️ You can also delete a pipeline from inside the pipeline view by opening the pipeline and selecting Delete from the top-right menu.

#### Running a Pipeline <a href="#running-a-pipeline" id="running-a-pipeline"></a>

![](https://docs.revvy.io/~gitbook/image?url=https%3A%2F%2F599358484-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FlcWbuZareqS9jci4Vs22%252Fuploads%252Fhf46fcmEJWofP0wuzdCd%252Fimage.png%3Falt%3Dmedia%26token%3D6e84df9b-0d57-4213-ad5f-97ec67fef6c6\&width=768\&dpr=4\&quality=100\&sign=38481702\&sv=2)

To run an existing pipeline:

1. From the **Pipelines** tab, click R**un pipeline**.
2. In the modal:
   * Select the **Branch** to deploy from.
   * Select the **Pipeline** to execute.
3. Click Run.

The pipeline will begin executing its defined steps (e.g., validation, testing, and deployment into connected orgs).

#### Pipeline Overview Page <a href="#pipeline-overview-page" id="pipeline-overview-page"></a>

When you open a pipeline, the **Overview Page** displays:

* **Pipeline Name** – Title of the pipeline.
* **Created By** – Who created it.
* **Branches** – Source branches linked to the pipeline.
* **Orgs** – Connected target orgs for deployment.
* **Last Updated** – When the pipeline was last modified or executed.

This gives administrators a clear view of pipeline configuration and execution readiness.

#### Example <a href="#example" id="example"></a>

* A QA team creates a **QA Team Pipeline** linked to the ReleaseBranch.
* Two orgs are connected: QA Sandbox and UAT Org.
* The team runs the pipeline after merging a pull request, automatically validating and deploying changes into both orgs.

#### Best Practices <a href="#best-practices" id="best-practices"></a>

* **Name pipelines by purpose** (e.g., Release-Branch-Pipeline, QA Team Pipeline).
* **Connect only required orgs** to reduce unnecessary runs.
* **Use branches strategically** – tie pipelines to stable integration or release branches.
* **Review activity logs** regularly to track deployment health.
* **Run pipelines after PR approvals** to ensure code quality and conflict resolution before promotion.
