Deployment Rollback

Deployment Rollback is a Rollback that reverses the effects of an identified deployment by restoring the affected deployment subject to its identified predeployment state.

A Deployment Rollback may apply to:

The predeployment state may be identified through:

Deployment Rollback differs from deployment cancellation:

  • Deployment cancellation stops a deployment before completion
  • Deployment Rollback reverses the effects already produced by a deployment

Deployment Rollback differs from deployment retry:

  • Deployment Rollback restores the predeployment state
  • Deployment retry performs the deployment operation again

Deployment Rollback may precede a corrected deployment or another recovery operation.

rollback that reverses the effects of an identified deployment by restoring the affected deployment subject to its identified predeployment state

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

Deployment Rollback does not imply that every deployment effect can be reversed.

Applicable requirements should identify:

  • The deployment subject
  • The deployment is being reversed
  • The predeployment state
  • The rollback initiation condition
  • The effects included in the rollback
  • Effects excluded from the rollback
  • The required rollback result
  • The generated Evidence

A Deployment Rollback may require separate handling for:

  • Persistent data
  • External services
  • Credentials
  • Messages
  • Transactions
  • Provider-managed resources
  • Changes performed outside the deployment boundary

A deployment replaces a Containerized Workload with an unacceptable Revision. Crucible performs Deployment Rollback by removing the new workload Revision and restoring the workload configuration and Image used immediately before the deployment.


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • dido/99_annexes/annex-b-terms-and-definitions/d/deployment_rollback.txt
  • Last modified: 2026/07/17 10:08
  • by nick_dido