---
schema_version: "1"
id: aa3b152de21a833a9a40cc77d8fdc8a284ce356bf4efe52fe60b598dba425d23
title: Build Your Pipeline Using the Template
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_template.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_build_template.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 721b96096296da52c4e6787734259d31e3e5aa33eac0ab9479bdd50cca228e89
description: When you specified the release target (production) environment, it automatically became the last pipeline stage. DevOps Center also associates it with the default branch in the source control repository, which is often called main by default. We don’t recommend that you edit the branch for this final pipeline stage.
products:
  - Salesforce Platform
release: "264"
---
# Build Your Pipeline Using the Template

When you specified the release target (production) environment, it automatically became the last pipeline stage. DevOps Center also associates it with the default branch in the source control repository, which is often called `main` by default. We don’t recommend that you edit the branch for this final pipeline stage.

![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. From the Pipeline page, start with the Staging stage.
2. Enter the **Stage Name**.
    
    Stage names can’t contain backslashes or double quotes.
3. Click **Connect Environment** to log into the environment associated with this stage.
4. 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 500 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.
5. Indicate which stage is the bundling stage, the stage where changes are grouped, versioned, and promoted together in downstream stages (1).
    
    In the template, the UAT stage is the bundling stage. The items you promote from integration are released together in a work item bundle in the next stage, UAT, and for all future stages.
    
    ![Pipeline Environments page that shows that UAT is selected as the bundling stage.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center_setup-264-0-0-production-enus/4741b024-a514-4bcf-8f2f-9d308932d2de/devops_center_setup/images/pipeline-bundling-stage.png)
    
    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 recommend a bundling stage.
6. Repeat this process for the rest of the stages.
7. [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.") (2).

To improve release quality, we recommend you set up and use [DevOps Testing](https://help.salesforce.com/s/articleView?id=platform.devops_testing_improve_release_quality_with_devops_testing.htm&language=en_US).