This section provides an overview of Deployment Automation snapshots and explains how to work with snapshots.

Snapshot overview

A snapshot represents a specific state of an application in an environment. Snapshots specify the combination of component versions that you are going to deploy together.

When a snapshot is created, Deployment Automation gathers together information about the application for a given environment, including the component versions, process versions, and properties.

Typically, the snapshot is generated in an uncontrolled environment, where there are no approval processes or gates defined.

After a snapshot is created, it can then be promoted through a deployment pipeline. For example, as the application moves through testing environments, Deployment Automation ensures that the exact versions are used in every environment. After all the appropriate stages and approvals for a snapshot are complete, the snapshot is deployed to production.

Snapshots help manage complex deployments, such as deployments with multiple tiers and development teams.

Example: After testing and confirming that team A's component works with team B's, a snapshot can be taken. Then, as development progresses, additional snapshots can be taken and used to model the effort and drive the entire deployment, coordinating versions, configurations, and processes.

Back to top

Snapshot content

Snapshots include the following:

Component Versions When you create a snapshot, you can manually specify the version for each component, or you can copy the versions used in a specified environment or snapshot.
Configuration A snapshot contains the versions of the processes that have been designed, the properties that these processes use, and other information. From the configuration, you can view and set the versions of the processes and properties used in the snapshot.

You can apply a status to a snapshot, which typically indicates whether the snapshot has been deployed successfully to an environment.

You can use this status along with gates, which enable you to allow deployments to an environment only if the snapshot has reached a particular status.

Example: You could set the INT environment gate condition, so that if the status is set to Dev_Complete, the snapshot can be deployed to the INT environment.


You can lock snapshots when they are deployed to a particular environment, ensuring that nothing can be changed.

Typically, you lock a snapshot when it goes into a preproduction environment before being deployed to production.

Back to top

See also: