Deployment
How deployments work
Deployments involve packaging a release—which contains the software update or configuration—into a deployment. Once the deployment is created, it is rolled out to the target device groups. The deployment process ensures that updates are distributed across the device fleet in a structured manner.
Creating deployments
When creating a deployment, key parameters must be defined, such as target device group, software release, and deployment method. Once the deployment is initiated, Device Trust Manager monitors its progress and reports on the status of each device.
Scheduling deployments
Device Trust Manager allows you to schedule deployments in the following ways:
Deployment method | Description |
|---|---|
Deploy now | The deployment is initiated immediately and will apply to all devices currently in the group, as well as any devices added later. This deployment remains active until it either reaches a defined limit or is manually aborted. |
Monitoring and managing deployments
Once a deployment is active, you can monitor its progress or abort the deployment.
Deployment states
Deployments move through various states during their lifecycle, reflecting the current status of the deployment.
State | Description |
|---|---|
Active | The deployment is currently rolling out updates to devices. |
Completed | The deployment has finished, either because it has reached its defined limits or because all devices in the group have been updated successfully. |
Aborted | The deployment was manually stopped. Devices that haven't started the deployment will not receive it, but devices in progress will complete the update. |
Device-level reporting
Deployments can be tracked at the individual device level. The following sub-statuses to indicate the update’s state on each device.
Sub-status | Description |
|---|---|
Successful | All artifacts in the release have been successfully deployed to the device. |
Failed | The update failed after all retries were exhausted. |
Pending | The update has been created but has not yet started on the device. The device has not received the notification that an update is pending. |
In-progress | The update is currently being deployed to the device, including stages such as Downloading, Downloaded, Installing, Rebooting, and Retrying. NotaIf a device is unreachable, a deployment will enter the Retrying stage. Device Trust Manager will continue attempting the update until the defined timeout is reached, at which point the device transitions to a failed sub-status. |
Deployment failure handling
If a deployment fails, an automated rollback to a previous known good state occurs. Rollbacks are executed at the device level using rollback scripts that are included in the artifact.