Pipelines
Learn about SRE.ai's Pipelines feature
Overview
The pipeline is what turns your connected Salesforce orgs and GitHub repositories into a governed deployment workflow.
It defines the stages a change must pass through (from development to production) and the quality criteria each stage enforces.
Without a pipeline, SRE.ai has no structure for how code should move through your environments or when a deployment should be blocked.
Pipelines gives you a workflow builder for mapping how code moves from development through production.
Each pipeline is rooted in a repository and consists of stages, each mapped to a branch and one or more Salesforce environments.
Core capabilities

Templates
SRE.ai Pipelines feature offers three preset templates, known as release management strategies:
Release Flow: Structured, multi-stage promotion with formal QA and a dedicated hotfix path. Best for teams with scheduled release cycles.
Progressive Flow: Multi-stage validation with stricter quality gates at each step. Best for teams that need deliberate control over what reaches production.
Continuous Flow: Simplified, fast path from development to production. Best for teams practicing continuous delivery with rapid iteration.
Templates cannot be edited.
Templates consist of stages.

Stages
A stage is a highly customizable block that represents a discrete phase in your deployment lifecycle.
SRE.ai's Pipelines feature supports five customizable stages:
developer/ team/ project
code integration
staging
production
hotfix
The standard Pipelines' progression flows left to right.
An example of a Pipelines' flow:
developer/team/project → code integration → staging → production.

Environments
Environments are deployment targets within a stage.
Each environment:
Maps to a Salesforce org (your Production org, Sandbox, or Scratch Org)
Tracks deployment status and history
Can be promoted to parent stage environments
Salesforce org connections
Salesforce org connections represent your actual Salesforce organizations that SRE.ai deploys to.
SRE.ai supports two types of Salesforce orgs connections:
Regular Orgs:
Traditional fixed Salesforce orgs (Production or Sandbox) that can be assigned to specific branches.
Sandbox Pool Orgs:
Tied to PRs instead of specific branches. These orgs best serve developer workflows.
How it works
Template details
Each template creates a fixed stage hierarchy when a pipeline is first configured. The hierarchy determines the only valid promotion path for changes: from child stages up to their parent stage, working toward the root Production stage.
Stages form a tree, not a flat list. Changes must move through every level of the tree in order — skipping stages is not permitted.
Release Flow
For scheduled releases with formal QA processes
Continuous Flow
For rapid deployment and continuous delivery
Progressive Flow
For staged validation with enhanced quality gates
How branches map to pipeline stages
Each stage can be configured to connect to a specific branch in your repository.
When you configure a stage, you select which branch it tracks and which Salesforce environment(s) it deploys to.
A typical setup might look like this:
Development
develop
Developer sandboxes
Integration
integration
QA sandbox
Staging
staging
UAT sandbox, SIT environment
Production
main
Production org
You can connect multiple Salesforce orgs to a single branch.
As changes move through the pipeline, they can be deployed to one org or several, whichever fits your release process.
Deployment workflow
SRE.ai executes a structured workflow when you initiate a deployment:
Confirm Change: Verify which change (feature or fix) to deploy
Confirm Target Org: Auto-detect or select the deployment target based on the stage hierarchy
Check Quality Gates: Run automated quality checks against stage requirements
Deploy: Execute deployment to the target Salesforce org if all gates pass
Summarize Issues: If quality gates fail, provide a detailed issue summary for remediation
This workflow ensures that every deployment meets your quality standards before it is deployed to your Salesforce environments.
Deployment target enforcement
SRE.ai enforces that changes move through your pipeline in order. The deployment target is determined by the pipeline.
You cannot skip stages or deploy to an out-of-order environment.
The deployment UI only shows the next valid target for a given change. Invalid targets are not available.
A change's first deployment must always target the lowest stage in the pipeline (e.g., Developer or Code Integration).
Attempting to deploy to an incorrect target returns a clear error.
Setup
Reset and template selection
A Reset button is available in the top right corner of the pipeline workspace.
Use it to clear your current pipeline configuration and select a new template. This is useful when starting over or switching release management strategies.
To confirm the reset, you will be prompted to type the pipeline name before the action proceeds.
Initial setup
Setting up a pipeline requires two steps:
Select a repository to connect to

Select a template

Customization
All five stages share the same customizable attributes:
Developer/team/project
Code integration
Staging
Production
Hotfix
Read below to learn about their customizable attributes
Branch association
Each stage can track a specific Git branch.
Staging might track a "qa" branch while production tracks "main."
The branch indicator appears in the stage card's upper right corner
Environment mapping
The environments section shows which Salesforce orgs receive deployments when changes reach this stage.
You can search existing environments or add new ones. Multiple environments can be mapped to a single stage for scenarios like parallel QA testing.
Quality gates
Each stage enforces its own set of quality criteria that must be satisfied before changes can advance. Configure code review requirements, code coverage thresholds, test levels, and pull request requirements.
Notifications
Each stage can send notifications to email, Teams, or a webhook destination when specific pipeline events occur, such as deployment success, failure, or a new commit.
Quality gates
Configured at the stage level, quality gates define the criteria that must be satisfied before changes can advance.

Quality gates are enforced when the user attempts to move changes along the pipeline through chat.

The following gates are configurable per stage:
Stage notifications
Each stage can send notifications when pipeline events occur.
Stage connections
Pipeline connections define how changes move between stages.
Last updated

