Scheduling into Environments

After you associate a deployment path with a release package or deployable release train, you can then schedule the package or train into environments in the path.

The instance of the deployment path is specific to the package or train and cannot be copied to another. New packages and trains start with the original deployment path, and the specific schedule must be added for each release package.

To schedule into environments:

  1. In a release package, select the Deployment Path tab.
  2. In the table below the deployment path diagram, for each environment, click the schedule icon and select the date range and schedule owners.
  • Environments with approvals: if a schedule has been defined, the Start Deploy button is only displayed for dates that occur in that schedule. If the date is in the past, or needs to be modified or removed, re-schedule the environment and run the Recreate Approval transition.
  • Environments without approvals: schedules are for information only and are not enforced. If you click Start Deploy the deployment starts regardless of the scheduled date. Use deployment task scheduling to enforce schedules. See Scheduling Deployment Tasks.

Related Topics

Creating Deployment Paths

About the Environment Process App

Scheduling Deployment Tasks

Scheduling Release Trains

Scheduling Environment Events

Monitoring Scheduled Jobs