Overview → About the Solution Process Apps → About the Environment Process App
Environments represent a set of resources to which release packages may be deployed. Environments manage and give visibility into the scheduling of maintenance and other events in environments, flagging any scheduling conflicts. Release packages are scheduled into environments in deployment paths.
The Environment process app includes two applications: Environment and Environment Schedule. The Environment Schedule application includes the Environment Schedules and Path Elements workflows. The applications and their workflows are described in the following sections:
The primary application in the Environment process app is Environment.
Release engineers typically own environments.
Release engineers and release managers can do the following for environments:
Environment items are created. Each environment must be owned by a release engineer.
Environments are placed online, signaling that scheduling can take place for release packages, maintenance windows, and other environment events, such as events for release trains.
The environment owner can take environments offline for maintenance and return them back online when maintenance is complete.
The Environment Schedule application implements the environment scheduling process.
When an event is scheduled for an environment, the scheduled event can be required to go through an approval process. If you schedule the environment in a time period that overlaps, you'll get an error. The error is highlighted on the schedule and notifications go to those subscribed.
The Environment Schedule application manages the following:
Environment schedule items are created. The environment schedule is owned by the submitter or a release engineer.
If approvals are required, the environment schedule item must be approved by a release engineer or release manager.
The environment schedule is started.
When the environment item leaves the deployment state in the workflow, the environment schedule is completed.
The environment schedule is complete.
The Path Elements workflow is implemented in the Environment Schedule application.
The individual environment items in a deployment path are stored in the Path Elements project. The path element items act as templates and are not associated with a specific release package. When a deployment path is used in a release package, duplicates are made of these path element items and associated with the specific release package. The new items are created in the Environment Schedules project.
Copyright © 2012–2016 Serena Software, Inc. All rights reserved.