liveBook · Manning

Software artifact

A software artifact is a persistent work product or object produced, maintained, or consumed during software development or operation.

How 5 Manning books explain it

GitHub Actions in Action: Continuous integration and delivery for DevOps

A software artifact is a generated file or package retained or transferred as an output of a development workflow.

How it is used
Packages CI outputs for retention, release, and transfer into deployment workflows.
How deep it goes
Explains artifact creation, storage, release attachment, deployment-file preparation, and retention configuration rather than artifact format internals.
Examples
Uses .NET binaries, container images, Kubernetes YAML with image-tag tokens, and an uploaded file retrieved by a deploy job.
What you can do after
Operate/configure artifacts for workflow transfer, release handoff, deployment traceability, and storage-cost control.

Read how GitHub Actions in Action: Continuous integration and delivery for DevOps explains software artifact →

Platform Engineering on Kubernetes

A software artifact is a produced, versioned deliverable such as a package, image, binary, or deployment manifest.

How it is used
Connects source changes to publishable service versions that later delivery steps can consume.
How deep it goes
Details build, test, version, and publication steps plus repository requirements, but leaves deployment to later automation.
Examples
Uses a tagged binary, amd64 and arm64 container images, a Dockerfile, and distributable Helm Charts.
What you can do after
Operate/configure a service pipeline to publish traceable binaries and images for later deployment.

Read how Platform Engineering on Kubernetes explains software artifact →

Vibe Engineering

An artifact is a concrete output produced by a software or AI process that can be passed to or consumed by another process.

How it is used
Coordinates orchestrated agent workflows through inspectable handoffs, verification checkpoints, and human review.
How deep it goes
Defines artifacts and explains their compression, verification, versioning, traceability, and audit roles.
Examples
Uses design documents, code, decision summaries, test results, coverage analysis, documentation diffs, and changelog entries.
What you can do after
Operate agent pipelines by handing off structured outputs, checking them independently, and tracing failures across workflow boundaries.

Read how Vibe Engineering explains software artifact →

Automating API Delivery

A software artifact is a generated build output, such as compiled code, a release package, or an SDK, that can be stored and delivered.

How it is used
Coordinates build outputs between CI generation, repository storage, downstream delivery, and environment promotion.
How deep it goes
Distinguishes generated output, repository storage, immutable metadata, and promotion, without detailing artifact packaging internals.
Examples
Uses compiled code, release candidate packages, SDKs, OpenAPI definitions, Avro schemas, and archived build output.
What you can do after
Operate/configure repositories and registries to archive, publish, retrieve, version, debug, and promote generated outputs.

Read how Automating API Delivery explains software artifact →

Shipping Go: Develop, deliver, discuss, design, and go again

A software artifact is a distributable result of software development, such as a library version, executable binary, or container image.

How it is used
Uses artifacts as the concrete output of a delivery pipeline and the point where customer feedback can begin.
How deep it goes
Explains artifact forms, release-candidate testing, delivery, deployment, and feedback without detailing build-system internals.
Examples
Uses library versions, executable binaries, container images, release candidates, IoT updates, and downloadable packages.
What you can do after
Evaluate/understand how code becomes a distributable artifact and distinguish shipping it from deploying it.

Read how Shipping Go: Develop, deliver, discuss, design, and go again explains software artifact →

Also covered in

What to know first

Related concepts

Questions about software artifact

What is software artifact?

A software artifact is a persistent work product or object produced, maintained, or consumed during software development or operation.

Which Manning books explain software artifact?

GitHub Actions in Action: Continuous integration and delivery for DevOps, Platform Engineering on Kubernetes, Vibe Engineering, Automating API Delivery and Shipping Go: Develop, deliver, discuss, design, and go again.

What should I know before learning software artifact?

Manning books that teach software artifact usually introduce deployment pipeline, AI agent, container and language model first.

What kinds of software artifact are there?

Kinds of software artifact include prompt, text artifact and tool description.

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.