Option DP – Deploy

Code Pipeline Deploy provides the capability to deploy software components into different execution environments and is a companion product to the base Code Pipeline product. The diagram illustrated in the following figure shows how the two products coexist. 

Option DP

Base Code Pipeline

The base Code Pipeline product provides Application Lifecycle Management functions (such as software configuration, change, and process management) using a promotional model. The Change Cycle is modeled by defining a hierarchy of levels where each level represents one stage in the cycle.

Each Code Pipeline lifecycle level can also be used as an execution environment that is directly managed as part of the Change Cycle. This eliminates the need for additional steps to maintain and deploy into separately managed execution environments.

Reasons to Use Code Pipeline Deploy

However, if an organization needs to separate the development and delivery of Application releases from their Deployment into the execution environments, Code Pipeline Deploy can be used.

How Does Code Pipeline Deploy Work?

The Code Pipeline Administrator defines the execution environments in Code Pipeline Deploy. It uses Deploy Requests as the mechanism for requesting and processing a software deployment. These Deploy Requests specify the software components to be deployed, the target execution environment, timing, and other processing constraints.

Code Pipeline Deploy will then process the request, according to the constraints specified, by distributing the components to the target Deployment Systems and activating them. At a minimum, this involves placing the component in the correct storage location—but could also include Adaptation of the component where necessary, as well as initiating other processes required to make the component active.

The Code Pipeline Administrator will define how Applications in base Code Pipeline are connected to the desired execution environments in Code Pipeline Deploy.

Deployment into an execution environment can be initiated automatically from base Code Pipeline. When Code Pipeline determines that deployment is necessary, it creates an appropriate Deploy Request that is then processed by Code Pipeline Deploy. The status of the Deploy Request is reflected in the Code Pipeline Task and Set status, and the full details of the Deploy Request can be easily accessed from base Code Pipeline.