Environment Management Options

You have several options to manage your environments from the environment’s menu in the Pipeline Environments tab. Which menu options are available is determined by the environment type and whether the pipeline is activated.

Managing Environments in Lifecycle Center

This topic is only for DevOps Center (Managed Package). In Lifecycle Center, you replace or remove environments. For details, see Manage Environments.

Swap Environment

Swap a development or pipeline environment with another after the pipeline is activated. Use this operation after a sandbox has been refreshed to re-establish the connection with DevOps Center.

Development environments—if DevOps Center can determine that the environment was descended from an environment in the project pipeline, all unpromoted work items that are connected to the current dev environment are moved to the new dev environment. If DevOps Center can’t determine the environment’s ancestry, DevOps Center deploys all changes from the first pipeline stage’s branch to the new dev environment.
Pipeline environments—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 the environment’s ancestry, DevOps Center deploys all changes from the pipeline stage’s branch to the new pipeline environment.

Remove Environment

Remove an unused dev environment from the list. If you change your mind, you can add a removed environment again. However, you can’t remove an environment after it has an activity history associated with it. After an environment has an activity history, your options are to disconnect it or swap it.

Disconnect Environment

Disconnect a dev environment that is expired or you no longer plan to use to remove it from the list. You can disconnect an environment only if no active work items are associated with it. After it’s disconnected, you can still view information about the environment in the Activity History but you can’t use it again in the DevOps Center project. You can, however, use the environment in a different DevOps Center project.

Change Environment

Select a different environment for a pipeline stage, if the pipeline isn’t yet activated.

Add the Release Environment for the Project
At a minimum, projects require a release environment (often your production org) and one developer environment. Be sure all team members are users in this environment if they require access to it to perform deployments to it from within DevOps Center.
Add Development Environments to the Project
Add the source-tracked development environment that you created for each developer working on the project.
Update IP Allowlist for DevOps Center App
If your security settings require it, add the necessary domains for all environments that have allowlisting enabled.