---
schema_version: "1"
id: 63a794f51e564f01c537e11ae0b04289f42527ce233f54a41a2910e10b6cdee6
title: Decide How to Build Your 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.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_build.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0098ec463948a2b31e31fdcc555377c33047f7de951b8e60fd3f02bc0efd412a
description: After you define development environments and a release (production) org, you have a basic pipeline. However, it’s not recommended that you deploy directly to production. You can use our template to build the pipeline, you can add more stages to the pipeline template, or you can build your own.
products:
  - Salesforce Platform
release: "264"
---
# Decide How to Build Your Pipeline

After you define development environments and a release (production) org, you have a basic pipeline. However, it’s not recommended that you deploy directly to production. You can use our template to build the pipeline, you can add more stages to the pipeline template, or you can build your own.

While you’re working on building the pipeline, your changes persist but don’t get saved to the project until you activate the pipeline.

Complete the creation of the environments associated with each 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. Access the Pipeline page.
    
    1. From within the project, click **Pipeline**.
    2. From the All Projects page, click **Click to Create Pipeline**.
    
    In the Pipeline page, you see the pre-defined pipeline template.
2. Before you begin, it’s important to understand how to properly specify the branch for each pipeline stage.
    
    We recommend that you don’t share branches across projects.
3. Complete your pipeline configuration using the preferred method.
    - Use the provided template to build your pipeline.
    - Build your own pipeline configuration.

For best results:

- Stage names can’t contain backslashes or double quotes.
- Follow recommended practices when naming the branches associated with each pipeline stage.
- 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). DevOps Center can’t track changes across projects so unique branches ensure that conflicts don’t get introduced and changes don’t get overwritten.

#### See Also

- [Build Your Pipeline Using the Template](https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_build_template.htm&release=264.0.0&type=5 "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.")
- [Build Your Own Pipeline](https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_build_own.htm&release=264.0.0&type=5 "Quickly build your own pipeline by modifying the existing template pipeline.")
- [Best Practices When Naming Branches](https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_about_branches.htm&release=264.0.0&type=5 "Each pipeline stage has an associated branch in the source control repository, which contains the changes associated with your team’s work items. When building your pipeline, you can specify either an existing branch in the repository, or allow DevOps Center to create one for you. If you allow DevOps Center to create it for you, indicate a unique alphanumeric string.")