Deployment schedules

Use deployment schedules for continuous deployment of packages to multiple deployment servers. Using deployment schedule, you can continuously deploy packages from one server to another at the scheduled time.

You can configure a notification process to notify the success or failure of the deployment schedule.

Once a deployment schedule is active, the system kicks in the next scheduled time.

When the scheduled time for an active deployment is reached:

• If the deployment is successful, an audit log entry is recorded in the deployment schedule history showing the status as 'Complete'.

• If the execute test plans is set to 'true' and when the test case fails, then no deployment takes place. An audit log entry is recorded showing the status as 'Failed'.

• If the package is deployed and if the deployment fails to one of the deployment servers, an entry is recorded for the failed servers and continue to the next deployment server (if any). For multiple deployment servers, errors for each server is recorded in the audit log entry showing the status as failed with all the error information of the failed deployments. If the deployment fails and if the "Allow solution rollback" system setting is selected, the solution is rolled back.

  You must have the necessary access control list permissions (Write or Full control) to configure a deployment schedule.

To learn how to add, edit and delete a deployment schedules, see Manage a deployment schedule.