Each pipeline stage in the next-generation DevOps Center has an associated branch in your
source control repository that contains the changes for your team's work items. When you build
your pipeline, let DevOps Center create a branch for a stage, or specify an existing branch in the
repository.
Required Editions
Available in: Lightning Experience in Professional (API access required),
Enterprise, Performance, Unlimited, and Developer
Editions
Not available in: Government Cloud Plus. Contact your Salesforce account
executive for more details.
Not available in: EU Operating Zone. EU Operating zone is a special paid
offering that provides an enhanced level of data residency commitment. DevOps Center
is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms
and conditions.
User Permissions Needed
To specify a branch for a pipeline stage:
DevOps Center Admin
If you let DevOps Center create the branch, provide a unique alphanumeric name. We recommend
that branch names use:
All lowercase letters
60 characters or fewer
Hyphens or underscores as separators (no spaces)
Both letters and numbers, but not all numbers
Important If you share branches across projects, you can experience unexpected
behavior, particularly if changes are made to the branches outside of DevOps Center.
A branch must be sourced from the next stage's branch (right to left). For example, if your
release environment's branch is main, then the branch for the pipeline stage to
the left of it, Staging, must be created from main. The branch for the pipeline
stage to the left of Staging, UAT, must be created from staging. DevOps Center
handles this sourcing for you when it creates the branch.
Go to the DevOps Pipelines tab, and select your pipeline.
Locate the pipeline stage, and click Specify Branch.
From the Add Branch window, assign a unique branch to the pipeline stage.
To let DevOps Center create a branch, select Create a branch from main for
this stage, and enter a unique name in Branch
Name.
To use a branch that already exists in your repository, select Use an
existing branch for this stage, and enter the branch name in Branch
Name.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
