A task represents a business-meaningful activity that is associated with a software deployment. Each task is defined on a separate row in a deployment plan. During a deployment, you run tasks defined in the deployment plan to complete the deployment.

Most tasks have a starting and ending point, and a measurable duration. A task can have other attributes depending on its type. A task can be of one of following types:

Automation tool used for configuration management, application deployment, intraservice orchestration, and provisioning tasks.
Represents a critical event that happens at a specific time.
Sends an email message.
an organizational element. For example, you might use a header task to identify a task group.
Runs a Jenkins® job or pipeline.
Represents any activity that is associated with a software deployment, such as taking a server offline or updating a database. Users assigned manual tasks can be sent email notifications when their tasks start or fail.
Run a Shell Script
Shell script tasks are used to execute a sequence of commands. The shell is the command line interface (CLI) for the operating system (OS) used to interpret the sequence of commands communicating with the software interface.
Run another plan
Runs deployments for other deployment plans participating in the same release event. This is an experimental task type.
Creates and manages ServiceNow tickets.
HCL Launch (requires HCL Launch integration)
Use this task to run an HCL Launch application process.
HCL Launch Status (requires HCL Launch integration)
Use this task to add a status to all component versions contained within an HCL Launch snapshot.
Wait for approval
Pauses a deployment until the designated users approve the task.
You can add tasks to deployment plans by one of the following methods:
  • Create a new task
  • Import from CSV files that are created by UrbanCode Release or another application
  • Copy tasks from other deployment plans
Additionally, tasks are auto-created when you add an application to a pipeline.