Artifact

An artifact is a file or package produced during the process of building or deploying software. It is the output that gets stored, shared, or delivered so it can be tested, deployed, or released.

What It Means in Simple Terms

Think of an artifact as the finished product after software is built. Just like baking a cake produces a cake you can serve, building software produces artifacts that can be used or shipped.

Common Examples

A compiled application file
A Docker image used to run an app
A JAR or WAR file for Java applications
A ZIP file containing a website
A library package published for others to use

For example, when a developer pushes code and a build runs, the result might be a Docker image saved in a registry. That image is the artifact.

Why Artifacts Matter

Artifacts make software repeatable and reliable. Once an artifact is created, the same version can be tested, deployed, or rolled back without rebuilding it.

This helps teams:
Avoid “it works on my machine” problems
Ensure consistency across environments
Track exactly what version is running
Roll back quickly if something breaks

Where Artifacts Are Stored

After software is built, the resulting artifacts need a safe and organized place to live so they can be reused later. These places are called artifact repositories or registries. They act like warehouses for software outputs.

Why Storage Matters

Storing artifacts allows teams to:
Reuse the exact same build across environments like testing and production
Avoid rebuilding the same software multiple times
Track versions and changes over time
Control who can access or publish artifacts

Instead of emailing files or rebuilding from scratch, teams pull artifacts from a central location.

Common Types of Artifact Storage

Docker registries

Docker registries store container images. A container image includes the application and everything it needs to run.
Example: After building an image called my app v1.2, it is pushed to a registry. Servers then pull that exact image to run the app.

Popular Docker registries include Docker Hub and cloud provider registries.

Nexus

Nexus is a repository manager that stores many types of artifacts such as Java packages, npm packages, and Docker images.
Example: A team builds a Java application and stores the JAR file in Nexus so other services or teams can download the same version.

JFrog Artifactory

Artifactory is similar to Nexus but often used in larger or more complex environments. It supports many package formats and provides strong version tracking and security features.
Example: A company stores all its build outputs in Artifactory to ensure every deployment uses approved artifacts.

GitHub Packages

GitHub Packages allows teams to store artifacts alongside their code in GitHub.
Example: A team builds a library and publishes it to GitHub Packages so other projects in the same organization can use it.