Deploy a package to a deployment server

The Deployment opens in a new browser tab with the Deployment tab selected. The artifacts from the selected package along with the artifact name, type, version, and value are displayed.

The package is exported using the settings saved in the package and imported to the deployment server applying the import options. When a deployment schedule reaches the next due date as defined in the deployment schedule (see Manage a deployment schedule):

• If the deployment succeeds, the package in the deployment schedule is automatically deployed to each server and an audit log entry is added under the package category to record that the deployment is successful. The notification process creates a new job only when the "Notify on success" option is selected in deployment schedule.

• If the deployment fails, the results are recorded in the Results tab and display a summary of errors and warnings. An audit log entry is added under the package category to record that the deployment has failed. The notification process creates a new job.

• If the deployment to one of the deployment servers fails, an audit log entry for the failed server is added, and deployment to next server if any, continues. If there are multiple deployment servers then the errors for each server are recorded in the audit log. If the deployment fails or any error occurs on deployment, and if you have selected the Allow solution rollback system setting, the Rollback solution button appears. To roll back the solution, click Rollback solution.

  If any error occurs during rollback, you can Retry or Cancel the solution rollback. An audit log entry is added for the solution rollback. For more information on items that can be rolled back, see Solution rollback items.