Skip to main content

​
Version Sequencing

Version sequencing policies determine how Ctrlplane handles pending deployments when a new version is created. This prevents deployment conflicts and maintains infrastructure stability.

​
Available Strategies

  • Cancel Pending Deployments
    • When activated: Immediately cancels pending jobs for older versions when a new version is triggered
    • Best for: Environments where only the latest version matters
    • Example use case: Development environments where you want to skip intermediate versions and always deploy the latest
  • Await Pending Deployments
    • When activated: New version deployments wait for pending deployments to complete before starting
    • Best for: Production environments requiring sequential, complete deployments
    • Example use case: Systems with database migrations that must execute in version order

​
Configuration

Configure version sequencing at the environment level via policies:
  1. Navigate to Environment Settings → Policies
  2. Add or edit the Version Sequencing policy
  3. Choose your preferred strategy
  4. Save your changes

​
How It Works

When you create a new deployment version v2.0.0: Cancel Pending Deployments:
  • Any jobs for v1.9.0 that haven’t started are cancelled
  • Resources immediately begin deploying v2.0.0
  • Useful when intermediate versions can be skipped
Await Pending Deployments:
  • Jobs for v1.9.0 complete first
  • Once v1.9.0 finishes, v2.0.0 begins
  • Ensures all versions are deployed in order

​
Benefits

  • Prevents deployment collisions
  • Ensures correct execution order
  • Maintains deployment history
  • Reduces risk during complex deployments
  • Supports different deployment strategies per environment