Run deployment package processes

Deployment packages typically deploy artifacts for multiple applications.

For more details about deployment, see Run deployment processes.

To run a deployment package process:

  1. Navigate to Management > Deployment Packages.

  2. Select a deployment package.

  3. Click Run. The process wizard is displayed.

  4. If the deployment package has a pipeline associated with it, select an execution type. Click Next.

  5. If prompted, select one or more environments in which to run the package. These may be limited based on the pipeline or environment you select.

    • If you selected Do not use pipeline, selected environments do not initiate a pipeline execution even if you select the first environment in the pipeline.
    • If you select multiple environments, they are executed in parallel and steps that do not have environments use the same set of environments.
    • The list shows environments that have application environment counterparts in all used applications. If you select Show all available environments, environments that are used in at least one of the used applications are added to the list.

    Click Next.

  6. If prompted, enter or select values. The selections for versions, snapshots, and other properties are taken from the application or component process properties.

  7. Click Submit to start the process.

    When a process starts, the Request page opens where you can review the progress. The status of each step is displayed in color on the process graphic. Information for each step is displayed in the process list.

    • Blue: Waiting to start
    • Yellow: Running
    • Green: Succeeded
    • Red: Failed
    • Grey: Canceled
  8. For more details, see Analyze deployments.

    People notified for any approvals must approve or reject. See Approve requests.

Note: If gate conditions are defined for a target environment, the component versions or snapshots are deployed into that environment only if their status meets those conditions. For details, see Create gates.

Back to top

See also: