Add source-tracked development environments for team members in the next-generation
DevOps Center. You can add a development environment manually from the pipeline, or automatically
when your team members commit changes from DX Inspector.
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 add a development environment:
DevOps Center Admin
Before you begin, complete these tasks.
Create source-tracked Developer or Developer Pro sandboxes from your production org. Turn on
source tracking in production, and then refresh existing sandboxes. Or turn on source tracking
in specific sandboxes in Sandbox Settings (refresh not required).
Add team members as users to each development sandbox.
Collect login credentials for each sandbox.
Note Scratch orgs have source tracking enabled by default.
Go to the DevOps Pipelines tab, and select your pipeline.
Locate the Development Environments stage in your pipeline.
Click Add Development Environment.
In the Add Environment window, enter an environment name.
Click Connect.
Log in to the sandbox, and authorize the connection.
The development environment appears on your pipeline.
(Optional) To view details about a development environment, go to the Work Items tab, open
a work item, and view the associated development environment details.
Next, determine your pipeline configuration (how many stages), and then add the other
environments associated with your pipeline stages.
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.
