NEW
Practices and tools for storing, versioning, scanning, and distributing build, data, and model artifacts across environments.
DESCRIPTION
Artifact management governs the lifecycle of binary outputs—packages, containers, models, and other deployables. It ensures artifacts are versioned, immutable, scanned for vulnerabilities, and promoted across environments under policy. Centralized repositories integrate with CI/CD, enforce retention, provenance, and license compliance, and expose APIs for retrieval. In MLOps, artifact management covers model versions, datasets, and lineage. Strong artifact management is foundational to reproducibility and software supply chain security.
ALTERNATIVE DEFINITIONS
Wikipedia
A software repository, or “repo” for short, is a storage location for software packages.
Defines the storage locus central to artifact management.
Sonatype
A repository manager is a dedicated server application designed to manage all of the binary artifacts for a software organization.
Describes the managing server underpinning artifact management practices.
RELATED TERMS
Artifact Repository Container Registry Build Pipeline Continuous Integration Software Supply Chain Binary Promotion Bill of Materials Vulnerability Scanning Releasing
COMPETING TERMS
Package Management Object Storage
KNOWLEDGE AREAS
Platform & Tooling Software Engineering MLOps Data Engineering
TARGET AUDIENCE
DevOps Engineer MLOps Engineer Software Developer Data Engineer Application Administrator IT Manager
EXTERNAL SOURCES
- Wikipedia - Software repository
- JFrog - Artifactory overview and concepts
- Sonatype - Repository manager overview
- Google Cloud - Artifact Registry service overview
- Microsoft - Azure Artifacts overview
TOP QUESTIONS
Why is Artifact Management essential for DevOps?
It ensures reproducible builds, immutable deployments, and secure supply chains. Centralized control improves traceability and compliance.
Category: Relevancy
How does Artifact Management differ from Package Management?
Package management installs dependencies on hosts; artifact management stores and governs produced binaries across environments.
Category: Comparison
What policies should govern artifacts?
Retention, immutability, promotion rules, vulnerability and license scanning, and provenance (SBOM, signatures) are key.
Category: Best practices
How do artifacts support MLOps?
Models, datasets, and feature sets are versioned and promoted with lineage, enabling reproducible experiments and safe rollbacks.
Category: Example
What is a common mistake in Artifact Management?
Storing binaries in source control or ad hoc storage leads to poor performance, duplication, and missing metadata.
Category: Mistakes
How to secure artifact distribution?
Use signed artifacts (Sigstore), TLS, scoped tokens, network policies, and zero-trust access via proxies or gateways.
Category: Security
Which metrics indicate healthy Artifact Management?
Cache hit ratio, download latency, vulnerability remediation time, and promotion lead time reflect performance and safety.
Category: Observability
What’s a hot topic in Artifact Management?
Software supply chain security: SBOMs, provenance (SLSA), and artifact signing are rapidly standardizing.
Category: Topic
How do artifact repositories integrate with CI/CD?
Pipelines publish artifacts with metadata, trigger promotions, and consume versioned assets for builds and deployments.
Category: Integration