Pipeline Overview

This page explains how to view, create, and run pipelines in Revvy. Pipelines help automate deployments by connecting branches to target orgs and running defined release steps.

Pipelines in Revvy 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.

Pipelines List View

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

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

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

To run an existing pipeline:

1. From the Pipelines tab, click Run 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

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 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

• 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.