---
schema_version: "1"
id: 0f3a227befb94c2860615fd0e6892bbe8c673eba99bbd29c81e4a531b0a23a27
title: Build Your Own Pipeline
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_pipeline_build_own.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_build_own.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 533e0b018dcd3840cea8720ec97dce48b3ae5826340c8c863ad46c867d6346a3
description: Quickly build your own pipeline by modifying the existing template pipeline.
products:
  - Salesforce Platform
release: "264"
---
# Build Your Own Pipeline

Quickly build your own pipeline by modifying the existing template pipeline.

- From the Stage dropdown, move stages left or right, or remove a stage.
- Change the stage name.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center_setup-264-0-0-production-enus/4741b024-a514-4bcf-8f2f-9d308932d2de/images/icon_important.png)

Important Although you can use the same source control repository across DevOps Center projects, be sure the branches for each project are unique. If you re-use branches across projects, you risk overwriting changes and introducing conflicts.

1. Starting with the last stage before your release stage, enter the **Stage Name**.
    
    Stage names can’t contain backslashes or double quotes.
2. Click **Connect Environment** to log into the environment associated with this stage.
3. Next, click **Specify Branch** to indicate the branch associated with this stage.
    
    You can create a branch for this stage, or select an existing one. If you’re using the same source control repository as another DevOps Center project, branches must be unique for each pipeline stage, except for the release branch (often called main). Select an existing branch only if it isn’t being used in another DevOps Center project. DevOps Center can’t track changes across projects so unique branches ensure that conflicts don’t get introduced and changes don’t get overwritten.
    
    The Branch Settings dialog can display a maximum of 100 branches. If you don’t see the branch you want to select in the dropdown, delete any obsolete branches in the source control repository and try again.
    
    When you promote changes to this stage, the changes are merged to this branch, and DevOps Center knows exactly what to deploy to the associated pipeline environment.
4. Repeat for the rest of the stages.
5. Indicate which stage is the bundling stage, the stage where changes are grouped, versioned, and promoted together in downstream stages.
    
    See [To Bundle or Not to Bundle, That’s a Great Question](https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_bundling_stage.htm&release=264.0.0&type=5 "The process and mechanism for promoting changes from one stage to the next can vary as you move from “left to right” in the pipeline. In the earlier (left) stages of the pipeline, you often want more flexibility to promote individual work items from one stage to the next. As you move to the later (right) stages of the pipeline, it’s often desirable to have more predictability and ability to version the sets of changes that are promoted and ultimately released.") for why we recommended a bundling stage.
6. [Activate the Pipeline](https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_activate.htm&release=264.0.0&type=5 "A pipeline is ready for your team to use after you activate it.").