The Deploy application task

The Deploy application task reads an application or test artifact from a repository and deploys the application on an environment. This task is available in the Deployment, Upgrade, and Business change pipelines.

The Deploy application task performs the following actions:

• Exports the artifact from a repository
• Creates an application restore point
• Deploys application artifacts:
  • Dependent artifacts
  • Test artifact
  • Application artifact

The Deploy application task can deploy three types of artifacts:

• Application artifact: Created from the product rule for a defined application on a deployment pipeline.
• Test artifact: Created from the product rule defined for a test application on a deployment pipeline.
• Dependent artifact: Extracted from a specified deployment of a specified pipeline in the Deployment pipeline. The configuration is added to the Dependencies section under Application details.

A test artifact is deployed only when you enable Deploy test artifact? on the Deploy application task configuration for a stage. For more information on deploying a test artifact on the required stage, see configure test cases on a pipeline.

Check your knowledge with the following interaction.

You configure a pipeline with a development and production repository. The Deploy application task exports the application artifact from a development repository. Deploy application task is required to export a production-ready or ready-to-ship artifact, the task has to be configured to read the artifact from the production repository.

To configure the Deploy application task to read an application artifact from a Production repository, you enable Deploy production ready artifacts? on the details of the task. You configure the production environment to use production-ready artifacts.

The Deploy application task can generate a warning or request user input. When the task requests user input, the course of the task depends on the user's action.

The Deploy application task handles the following scenarios:

• When an artifact has draft flows, the Deploy application task generates a warning post-deployment. The deployments with draft flows fail in a production environment.
• When a deployment encounters an aged update, users decide whether the aged update is skipped, overwritten, or handled manually.
• If an artifact has schema changes, the user can act to deploy the schema changes manually.