Skip to main content

​
Release Windows

Release windows define time periods when deployments are allowed in an environment. Jobs will only execute during these windows. Use cases:
  • Maintenance Windows: Only deploy during off-peak hours
  • Business Hours: Restrict production deployments to business hours when teams are available
  • Freeze Periods: Block deployments during critical business periods (e.g., Black Friday, end of quarter)
Example configurations:
  • Monday-Friday, 9am-5pm: Business hours only
  • Daily, 2am-4am: Overnight maintenance window
  • Exclude Dec 15-31: Holiday freeze period

​
Gradual Rollout

Gradual rollout policies spread deployment jobs across resources over a specified duration, rather than deploying to all resources simultaneously. Benefits:
  • Risk Mitigation: Detect issues early before full rollout
  • Resource Protection: Avoid overwhelming infrastructure
  • Monitoring Time: Observe deployment impact progressively
Configuration:
  • Duration: 10m, 1h, 4h, 1d
  • Default: 0ms (immediate, all resources at once)
Example: With 1h duration and 60 resources, jobs will be triggered approximately every minute.

​
Deployment Cooldown

Deployment cooldown enforces a minimum time period between successive deployments to the same resource in an environment. Benefits:
  • Stability: Allow time to observe deployment impact
  • Issue Detection: Prevent hiding problems with rapid redeployments
  • System Health: Avoid overwhelming systems with rapid changes
Configuration:
  • Duration: 5m, 30m, 2h, 1d
  • Applied per-resource in the environment
Example: With 30m cooldown, after deploying v1.2.0 to a resource, version v1.2.1 cannot deploy to that resource for 30 minutes.