DORA and DevOps

Deployment path

Also known as Production deployment path, Release path

By WeavePublished 1 min read

Definition

A deployment path is the sequence of decisions, checks, environments, approvals, and automation through which a software change moves from a validated state to production. It includes the events that release the change and the feedback that confirms or rejects the result.

A path has stages and policies

The deployment path may include build, test, artifact creation, security checks, environment promotion, approval, rollout, and post-deployment observation. A change can be ready in the repository and still wait for a release window or a specialist decision.

Make each boundary explicit. A deployment attempt, a successful deployment, a feature exposure, and a rollback are different events. A pipeline retry can also create several records for one intended release. Consistent event definitions make comparisons more useful than apparent precision.

Measure flow and recovery

Inspect time spent in each stage, queue age, deployment frequency, change lead time, failure rate, rework, and recovery time. A faster deployment path is valuable when it maintains or improves stability. Removing a check may reduce waiting while increasing risk, so quality and operational outcomes belong in the same review.

Compare similar services and release classes. A mobile release with an external approval path should not be ranked against a small internal service using the same deployment boundary without context.

How Weave can help

Weave supplies development context around the changes entering the deployment path. Teams can inspect pull request size, review rounds, code quality, and rework alongside release results. This helps identify a likely upstream cause while deployment and incident systems establish what happened in production.

How this relates to Weave

Weave can connect development events before deployment with delivery benchmarks to help teams investigate where a deployment path creates waiting, rework, or quality risk. A deployment system remains the source for production event timing and outcome classification.

Explore Engineering intelligence

Sources and further reading

  1. DORA value stream management for software delivery
  2. DORA's software delivery performance metrics