Artifact repository
An artifact repository is a service that stores, versions, and distributes software packages, build outputs, container images, or other versioned artifacts.
Automating API Delivery
An artifact repository is a versioned repository service that stores and publishes software packages, binary artifacts, and their metadata for later consumption.
- How it is used
- Stores versioned build outputs so teams and downstream CI/CD stages can retrieve release candidates and SDKs without rebuilding them.
- How deep it goes
- Defines repository contents and benefits, then walks through publishing a generated Java SDK; leaves full deployment-pipeline implementation out of scope.
- Examples
- Shows a GitHub Actions step running Maven deploy and checking GitHub Packages for the published Java client.
- What you can do after
- Apply it via GitHub Actions, Maven, and GitHub Packages to publish a generated SDK for later consumption.
Read how Automating API Delivery explains artifact repository →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
An artifact repository is a service that stores, versions, and distributes packaged software or infrastructure artifacts.
- How it is used
- Distributes reusable infrastructure modules through controlled, versioned, and organization-accessible locations.
- How deep it goes
- Explains packaging, retrieval, mirroring, approval, and version pinning, but not artifact repository implementation details.
- Examples
- Uses packaged modules, internal mirrors, approved database versions, and Git tags such as v1.0.0 and v2.0.0.
- What you can do after
- Operate/configure it to publish, mirror, pin, approve, and distribute specific infrastructure module versions.
Platform Engineering on Kubernetes
An artifact repository is a repository service that stores, versions, and distributes software artifacts.
- How it is used
- Supplies a destination for pipeline-built binaries so later steps and other systems can consume them.
- How deep it goes
- Explains binary publication, tag-aligned traceability, credentials, and network access, but not repository setup.
- Examples
- Shows a built binary copied over the network and published using the source repository tag’s version.
- What you can do after
- Operate pipeline publishing by providing valid credentials and ensuring repository network access.
Read how Platform Engineering on Kubernetes explains artifact repository →
Related concepts
- Gradleused by · Gradle is an open-source build automation system for defining and executing software build tasks, managing dependencies, and configuring project builds.
- deployment pipelineused by · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
- software artifacthas part · A software artifact is a persistent work product or object produced or maintained during software development or a related workflow.
- Mavenused by · Maven is a build automation and project-management tool that manages dependencies and standardized build lifecycles, especially for Java and other JVM projects.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.