About Environments

Environments represent a set of resources to which turnovers are deployed. Environments can be reserved for release trains and linked to stage gates. Turnovers can then be scheduled for reserved environments.

Release engineers typically own environments. They schedule maintenance and decommission environments as needed. Release managers can also perform these tasks.

Each environment has a schedule view that shows all turnovers and scheduled maintenance for an environment. Scheduled events are also stored in the Environment Turnover Events auxiliary table.

You can link each Release Manager environment to a Release Automation environment. You can create new Release Automation environments from Release Manager or you can link to existing environments. For details, refer to Release Automation Deployment Features.

Note: Environment data is synchronized from Release Manager to Release Automation, but changes made to environments in Release Automation are not synchronized back to Release Manager.

Participants:

Release engineers
Release manager

Environments follow a process organized into these stages:

Provision
Release managers or release engineers create logical environments and link them to a new or existing Release Automation physical environment. Each environment must be owned by a release engineer.
Active
Once environments are placed online, they can be reserved for release trains. Turnovers and maintenance can be scheduled.
Inactive
The environment owner, typically a release engineer, can take environments offline for maintenance, and return them back online when maintenance is complete.
Environments that are no longer needed can be decommissioned.