Deployment Detail Page

About Deployment

Deployments are created automatically when a BuildCompleted event occurs in the Event Bus. In the event, we receive the Deployment Strategy and the Cloud variables. DCP then queries our Deployment Targets table to select a list of environments to create phases for and list of cluster targets to release to.

The model is this:

• Deployment
  • Phase(s) - per environment
    • Release(s) - per cluster

This feature lists details of the deployment.

• Deployment name. This is simply a friendly name to refer to a deployment by. A guid is a mouthful.
• Service: the service name that owns these deployments.
• Status: overall status of the deployment. See Deployment Statuses.
• Started: time when the deployment started.
• Started: time when the deployment stopped.
• Version: the artifact version as tagged in Github. This is a link to the Github tag.

Below the deployment details, is a list of phases defined for the deployment. The phase list shows:

• The phase name and the current status, for at-a-glance use.
• Approve and Reject buttons, if human approval is required.
• Cancel button - to cancel a specific phase. Cancelling a phase will also cancel the parent deployment.

Clicking on a phase, you then see the Phase Details and the Release List for the selected phase.

Phase details are:

• Phase ID: the internal identifier for the phase. Helpful to have this for debugging with logs and MonC. A helpful button lets you copy the ID to your clipboard.
• Status: the phase status. See Phase Statuses
• Started: time when the phase started.
• Started: time when the phase stopped.
• GUS Case ID: this links to the GUS case created, if a GUS case is required for approval.
• Created: when the phase was created.
• Updated: when the phase was updated.
• Status Detail: in some scenarios, such as a cancellation or a failure, DCP will store additional details in the Status Detail. This field is hidden if empty.
• Environment Rules and Approvals: this lists the pre-requisites for phases into the given environment and any approvals for those pre-requisites.
• learn more at About Phases

The release list feature lists the release for a phase:

• Name: this is the name of the cluster.
• Status: this is the deployment status of the release. See Release Statuses
• Started: time when the release started.
• Started: time when the release completed.
• Created: when the release was created.
• Updated: when the release was updated.