Artifact promotion
Also known as Artifact promotion metric, Artifact promotion in DevOps
Definition
Artifact promotion is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
How to use the concept
Teams get more value from artifact promotion when the signal is connected to a concrete question: where does work wait, what failed, what reached users, or which safeguard reduced exposure? Keep raw events available so a summary can be checked against the underlying delivery history.
A concrete delivery example
Imagine a change moving through build, review, validation, and production. The timeline shows 20 minutes of execution, 90 minutes of queueing, and one overnight approval wait. A artifact promotion report should preserve those stages so the team can address the dominant delay instead of shortening a convenient but minor step.
Limitations and interpretation
Interpretation requires context. Artifact promotion can vary with service architecture, traffic, release strategy, and incident severity. Avoid comparing unlike populations or turning the number into an individual target. Use the result to choose an investigation and revisit the definition when the system changes.
Before acting on artifact promotion, compare the current observation with a compatible baseline and ask which underlying event produced it. Keep the raw records, counting policy, and ownership visible. When the signal changes, inspect the surrounding workflow for queueing, rework, failed checks, or recovery work. That practice makes the glossary term useful for diagnosis rather than a label attached to a dashboard.
How this relates to Weave
Weave's Engineering Intelligence can help teams examine artifact promotion alongside code, pull request, quality, and delivery context. That view is useful for finding the workflow behind a result and deciding what to investigate next. The underlying repository, deployment, incident, or observability system remains the source of truth for the event, and teams should confirm the available integrations before relying on any field.
Explore Engineering intelligence