Swap a Pipeline Environment

Swap a pipeline environment with another environment. If the pipeline environment is a sandbox that was recently refreshed, you must swap it before anyone can promote changes to the associated pipeline stage. The DevOps Center connection to the current environment is no longer usable.

Required Editions

Permission Sets Needed
To swap an environment:	DevOps Center Manager
To access the named credentials required to authenticate to the environment:	sf_devops_InitializeEnvironments

Important We recommend that all sandboxes are refreshed from the production (release environment), or cloned from a downstream pipeline stage.

1. In the Pipeline Environments tab, select Swap Environment from the environment’s menu.
2. To acknowledge the considerations, click I Understand, then Continue.
3. Select Log In to New Environment, then click Log In.
4. Complete the login process.

   The pipeline stage is disabled until the deployment is completed.

   • If DevOps Center can determine that the environment was descended from an environment in the project pipeline, all work items that are connected to the current pipeline environment are moved to the new pipeline environment.
   • If DevOps Center can’t determine that the environment’s ancestry, DevOps Center deploys all changes from the pipeline stage’s branch to the new pipeline environment. This operation can take a while.