Deployment Plan

Track both application and infrastructure changes in a release through the deployment plan. The deployment plan is comprised of the manual and automated tasks required to deploy a group of applications. A dashboard displays the time remaining in a release window; whether the release is on time, ahead of schedule, or late. The progress of the tasks associated with the release.

Tasks are assigned to individuals and to roles (or group responsible for an activity). These tasks are grouped into segments, which represent a set of activities that should be completed together. Drill into segments to see the individual tasks and task details, including whether they are manual or automated, the estimated start time and expected duration.

Import Deployment Plans

Most new users of UrbanCode Release have an existing implementation plan which they maintain in a spreadsheet. Deployment plans can be imported from a CSV file to save time when getting started with the tool

Reuse of Deployment Templates

Traditionally, deployment plans need to be started from scratch each time you want to release an application. In UrbanCode Release, you can set up a template that adjusts to what is needed for that environment. Only the steps that apply to the set of application in the release are enabled. For example, tasks that represent a one-time configuration change will not appear in subsequent deployments to the same environment.

Tasks discovered in lower environments are automatically suggested for inclusion in later environments, making preparing for a deployment quick and easy.

Configurable Notifications

Instead of waiting on a conference bridge or having to call in for a status report, users can configure notifications to be sent for specific events of interest. For example, an automated notification can indicate that it is time for a person to begin their work, or escalate in the case of a failure.

During the execution of the deployment, users will mark manual tasks as “started”, “complete”, or “failed” and leave comments. Automated tasks will begin and a link to the deployment status will be displayed, as well as, a link to the complete log in UrbanCode Deploy will appear in the automated tasks results.

View Deployment History

Deployment history and post mortem reports make it possible to drill down into a release to view individuals and manual or automated steps associated with the release. It is even possible to export the deployment plan to a CSV file to see the original estimated and actual deployment times for each activity.