Define Deployment Tasks

Deployment activities are defined by tasks. An individual task is a unit of work that can represent any business-meaningful activity associated with a release. Tasks can be configured to run just once, or every time the deployment plan is used. A task can be assigned to a user role or specific user; and if unassigned, can be claimed by anyone with the requisite role. Once a task is defined, it is added to the task library and becomes available for other deployments.

When a task is created, it is given a duration, which is an estimate of the time it will take to complete. UrbanCode Release aggregates task durations to calculate overall deployment times.

Tasks can be automated or manual. Automated tasks come from integrations with external tools. Application processes from IBM uDeploy applications, for example, are available as automated tasks in UrbanCode Release.

Manual tasks can represent any non-automated task, such as stopping or starting a server. Unlike milestones which are defined for the overall release, manual tasks (as well as automated tasks) are attached to a particular phase and segment. A segment can be considered a grouping of tasks intended to finish at the same time.

Typically, tasks are defined on the Scheduled Deployments page in the web application, but they can also be exported and imported (as CSV files).