About the Deployment Path Application

The Deployment Path application is included in the Release Package process app.

Deployment paths are a sequence of environments through which a release package must progress, such as development, integration testing, and production. This allows you to ensure that each release package has gone through the required testing stages before it moves to production. You can define whether each environment is required or optional on this path. You can also define when the release package is locked to prevent further changes, ensuring that what was previously tested is what is going to be deployed to your production environment.

Deployment paths can be associated with specific release types, which enable you to limit the selection of paths available for a release package. For example, you may have both "development" and "production" release types for your deployment paths. The "development' paths would be available to developers as they test their items on the development and QA servers. The "production" paths would be available to release engineers and would allow the release packages to be deployed to staging and production environments.

The deployment path is designed using the graphical interface to add, modify, and delete the environments in the paths. For example, a simplified environment sequence would be the following:

An example deployment path is shown in the following figure.


  1. Each environment is represented by a box. An R in the bottom left of the box means the environment is required.
  2. A successful deployment moves a release package to the next environment in the state.
  3. If an environment allows redeploy, a returning line appears at the top of the diagram.
  4. Failure selections are shown on the bottom of the diagram.
  5. A lock icon indicates which environments are locked.

Deployment paths follow a process organized into these stages:


Typically, deployment paths are created when you implement Release Control for your organization. You generally have a limited set of deployment paths that should be available to use for your release packages, and those should be defined and ready to be selected by release engineers who use Release Control to deploy release packages.


While a deployment path is in the Create stage, release engineers can:


While a deployment path is in the Active stage, package creators, administrators, or release engineers:
  • can choose the deployment path when creating a release package
  • cannot make changes to the deployment path; to modify a deployment path, it must first be returned to the Create stage
Related Topics

Creating and Designing Deployment Paths

Configuring and Deploying Release Packages

About the Environment Process App