Skip to content
BENIBIX Learn

Build Artifact

Development☁️ DevOps & CloudDevOps Basics

Also known as Artifact (CI), Build Output, Release Artifact

The finished, saved output of a build, ready to ship.

Think of it like

Think of it like a cake in a box with a label on it. It is ready to send, and you know which batch it came from.

Example

Jack's pipeline builds once and saves web-1.4.2.zip. Staging tests that zip, and an hour later the same zip goes to production.

Why it matters

Building again for each step can sneak in changes. One saved artifact means you ship what you tested.

Definition

A build artifact is the finished output of a build, saved so it can be shipped. It might be a zip file, a folder of web files, an app installer or a container image. Each one is tagged with the version or commit it came from. The same artifact moves from testing to the live site, without being built again. That way, what was tested is exactly what goes live.

Common mistake

Building the code again for the live site after testing it. The new build may pull in a newer package.

Key takeaways

  1. 1
    The finished output. Saved, not thrown away.
  2. 2
    Tagged with a version. You know where it came from.
  3. 3
    Build once. Ship the same file everywhere.