Creating Environments

Environments represent a set of resources to which deployable release trains and release packages may be deployed. Environments manage and give visibility into the scheduling of maintenance and other events in environments, flagging any scheduling conflicts. Deployable release trains and release packages are scheduled into environments in deployment paths.

Environments are created in the Environments process app. These are logical representations of the physical environments used by your organization. Typical environments include testing, staging, and production.

Users who are assigned to these roles in the Environments process app can create and manage environments:

To create an environment:

  1. In Work Center, click New.
  2. Search for the project that will store your environment, and then select the project to open a Submit form. (By default, the Environments project is used to store environments.)
  3. Fill out the required fields and any optional fields.
    • Select the accessibility of the environment as follows:
      • Standard: Release packages can be promoted into the environment by users other than the Release Manager.
      • Restricted: Only the Release Manager can promote release packages into the environment.
    • Select whether deployment approval is required. If Yes, approval will be required upon promotion to this environment.
  4. Click Submit.
  5. Click Place Online.


The tabs available from an environment once it is created are as follows:

Updating Environments

Once created, you can update environments as follows:

  1. In the Release Control application group left navigation, expand the Environments section and select one of the activities sections to display the desired list of environments.
  2. Select an environment and click the Update button to edit it.

Options available depend on the process app workflow. For details on the default workflow, see About the Environment Process App.

Related Topics

About the Environment Process App

Creating Environment Groups

Using Release Packages

Using Release Trains


Creating Approval Rules