Run deployments

A deployment is run by running the tasks that are defined in the deployment's segments.

The default deployment plan has two segments: Pre-Deployment Tasks, and Deployment Tasks. Segments are started manually, and, like tasks, can be run in parallel or serially. Start times are calculated from durations that are defined when the tasks were created.

Segments are displayed on the Scheduled Deployment page (Home > Scheduled Deployments > selected_deployment). The order in which segments are displayed is not the order in which they are run.

Segments can be added or deleted at any time, and can have other segments that are designated as prerequisites. A segment with prerequisites cannot commence until the designated segments successfully complete all their tasks. Segments can also be restricted by user role; only users with the specified executor role can initiate the segment.

Users that are assigned to tasks can perform them, and tasks without an assigned user can be claimed by any user with the proper role.

After you schedule the deployment, it is added to the Scheduled Deployments page. There, you can edit, delete, or investigate the deployment.

Verify Segment Prerequisites

Ensure that every segment designated as a prerequisite for other segments has completed successfully. A segment, including those segments running in parallel with other segments, cannot commence until its prerequisite segments successfully complete. All segments can have prerequisites except the first one.

Segments can also be restricted by user role; only users with the specified executor role can initiate the segment.

Verify Overall Schedule

Ensure that all tasks have the expected duration; segment length is calculated by using task durations. The order in which segments are displayed is not the order in which they are run. If tasks are missing or require modification, make sure that any new durations remain within the deployment's expected scope.

If approvals are required, make sure that expected approvers are available and ready to act.

Segments are started manually, and, like tasks, can be run in parallel or serially.

Assign or Claim Tasks

Tasks can be assigned to a role or to a specific user. Unassigned tasks can be claimed by anyone with the defined role.

Configure Notifications

Email notifications can be sent to users whenever user-defined trigger events occur. Notifications can be attached to plan, segment, or task, and set to trigger in several ways. Notifications can be sent when a deployment finishes or an approval is required, for example. Notification recipients are defined with the security system's (see IBM® UrbanCode Deploy Security) LDAP integration.

When you set up notifications, you select both the triggering events and the role, which is inherited from the security system. For example, it is common for an administrator or environment owner to be notified when a task or segment starts, ends, or experiences an error.

Monitor Deployments

The dashboard provides real-time feedback about your release from a centralized portal. It displays the release segments and indicates the segment currently in progress, as well as those segments that are already completed. In addition to running a deployment, you can add segments to the plan, and tasks to the segments.


Feedback