Adding Deployment Tasks

If you are integrating with a product that provides the ability to execute processes, such as SBM, Serena Deployment Automation, Serena Dimensions CM, or Serena ChangeMan ZMF, and have the corresponding plugin configured properly, you can add deployment tasks. Depending on your selections, the execution of the deployment task may deploy the associated deployment units to the target environment, it may execute an operation on the environment, or it may submit or transition a request in another system to signal that a given task must be completed.

Prerequisites: Before you can add a deployment task, you must have a connection to the integrating product.

You must also have a supporting plugin configured. Refer the plugin documentation on the Documentation Center.

Note: Deployment tasks are implemented using the provider plugin execution provider type.

To add a deployment task:

  1. In a release package, select the Deployment Tasks tab, and then click Edit Deployment Tasks.
    Note: For the Edit Deployment Tasks button to appear, you must be logged in as the Release Manager.
  2. On the form that opens, click +, and then select the provider plugin that you are using for the deployment task.
  3. Give the task a title and description.
  4. Fill out the required fields and any optional fields and then click Save.
Tip: You can also copy tasks from a task template or from another release package.

Updating Deployment Tasks

Once you have created deployment tasks, you can do the following in the Edit Deployment Tasks list:
  • Reorder tasks: Drag and drop to reorder. Move your cursor over the task you want to move, and when you see the move icon, drag and drop it where you want it.
  • Add deployment units to tasks: Edit, delete, or link to a deployment unit by clicking the corresponding icons beside the task title. Move your cursor over the title area to see the icons.
  • Skip tasks: Click the active environment name beside the deployment task you want to skip. It will be grayed out to indicate that the deployment task will not be run in that environment. Using this technique, you can inactivate the tasks for some environments and not others.