About the Environment Process App

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:

Environment

The primary application in the Environment process app is Environment.

Participants:

Release Engineer
Release Manager

Release engineers typically own environments.

Release engineers and release managers can do the following for environments:

Create (commission) environments.
Schedule maintenance or other events and decommission environments as needed. This blocks out periods of time when release packages cannot be scheduled for the environments.
Decommission environments that are no longer needed.

Process Phases:

Environments follow a process organized into these stages:

Provision
Environment items are created. Each environment must be owned by a release engineer.
Active
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.
Inactive
The environment owner can take environments offline for maintenance and return them back online when maintenance is complete.

Environment Schedule

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.

See Scheduling Environment Events.

Process Phases:

Environment schedules follow a process organized into these stages:

Schedule
Environment schedule items are created. The environment schedule is owned by the submitter or a release engineer.
Active
The environment schedule is started.

When the environment item leaves the deployment state in the workflow, the environment schedule is completed.
Inactive
The environment schedule is complete.

Path Elements

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.

Related Topics

Creating Environments

About the Deployment Path Application

Using Release Packages