Artifact Management
Immutable versioned outputs, promotion between repositories, and retention policy.
4 to work through
-
intermediate
A platform distributes large artefacts to many consumers. What does artefact management need beyond storage?
2 min answer -
intermediate Multiple choice
A team's registry holds every build artefact ever produced: 400,000 container images, 180 TB, growing 6 TB a month, and the storage bill is now material. Which retention policy should they adopt?
3 min answer -
advanced
A deployment in one region runs correctly and the same deployment in another fails with a missing configuration key. Both reference image `service:1.8.2`. The registry reports one digest for that tag. How do you diagnose this, and what is the fix?
4 min answer -
advanced
In July 2024 a CrowdStrike content update - not a sensor code release - caused Windows hosts to crash worldwide, with Microsoft estimating about 8.5 million affected devices. The sensor software itself had been through staged release. What does this teach about artefact management, and where would over-correcting be a mistake?
3 min answer
5 terms in this topic
Artefact Promotion
Moving the identical tested artefact between environments rather than rebuilding for each - so that what runs in production is what was tested.
practiceArtifact Promotion
Moving one immutable build between repositories as it earns trust, rather than rebuilding it for each environment.
toolArtifact Repository
The system of record for built binaries, container images and packages, holding immutable versioned artifacts with their metadata.
practiceContent Artefact Release
Applying full release engineering - versioning, staged rollout, health gates and a rollback path - to artefacts that are not code but are interpreted…
conceptMutable Image Tag
A registry tag that can be repointed to different content, so the same reference resolves to different artefacts over time or in different places - w…
Neighbouring topics
Delivery & Release Engineering
General material on getting a change from commit to production safely and often.
Pipeline Architecture
Stages, fan-out, caching, and the difference between a pipeline and a long script.
Build Reproducibility
Pinned inputs and hermetic builds, so one commit cannot produce two different artifacts.
Environment Strategy
How many environments earn their cost, what each proves, and what none of them prove.
Branching Models
GitFlow, trunk and release branches as delivery constraints rather than Git preferences.
Continuous Integration Discipline
Integrating to the mainline daily, and the test speed and review culture that requires.
Deployment Strategies
Rolling, blue-green, canary and shadow, and the traffic and state each one assumes.
Progressive Delivery
Separating deploy from release, and exposing a change to users in controlled increments.
Rollback & Forward Fix
When reversing is genuinely possible, and designing so that it usually is.
Database Migration Under CD
Expand-contract, backwards-compatible schema change, and migrations that cannot roll back.
GitOps
Declared desired state in version control, with a reconciler closing the gap continuously.
IaC Modules & Drift
Reusable infrastructure modules, state ownership, and detecting what changed out of band.
Policy as Code
Encoding standards as automated admission and plan-time checks instead of review comments.
Pipeline Secrets
Short-lived credentials, workload identity, and why the CI system is a prime target.
Supply-Chain Provenance
SBOMs, signed artifacts, attestation, and knowing what actually went into a build.
Deployment Gates
Automated verification between stages, and the difference between a gate and a delay.
Flow Metrics
Work in progress, flow time and flow efficiency — where a change waits rather than moves.
Change Management vs CD
Reconciling CAB-era controls with continuous delivery without pretending either away.
Multi-Region Rollout
Ordering regions, bake time, and stopping a bad change before it becomes global.