Maintain pipeline integrity by replacing an expired, deleted, or refreshed development
or pipeline environment in the next-generation DevOps Center. When you connect a new environment,
DevOps Center restores the complete branch state, including metadata and configuration data, to
keep it in sync with the pipeline.
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.
Considerations Before Replacing an Environment
Promote all work items before you refresh the sandbox.
Make sure that the new development environment has source tracking enabled.
When you refresh the sandbox, you lose changes in the development environment that
weren't pulled and committed to work item feature branches.
Committed but unpromoted changes remain in the feature branch but don't appear in the
new sandbox. To see them, promote the work items and then sync from the first pipeline
stage branch back to the sandbox. See Keep Your Development Environment in Sync.
DevOps Center pauses the pipeline stage activities during the replacement to prevent
conflicts. You can't promote or run back sync until the new environment is fully deployed
and verified.
Important We recommend refreshing sandboxes from the production (release)
environment, or cloning them from a pipeline stage or an existing development
environment.
Replace a Development Environment After a Developer or Developer Pro sandbox refreshes or a scratch org expires, the connection to DevOps Center becomes unusable. Replace the development environment in the next-generation DevOps Center to restore the connection. DevOps Center deploys the pipeline stage branch to the new sandbox so that you can continue working with the correct metadata and configuration data.
Replace a Pipeline Environment Activating a refreshed sandbox permanently deletes the original environment and its data, which breaks the connection to DevOps Center. Replace the pipeline environment in the next-generation DevOps Center before your team members promote changes to the associated pipeline stage. DevOps Center deploys changes from the pipeline branch to the new environment.
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.