CI/CDOptional

Artifacts & Caching

Speed pipelines with caching and manage build outputs.

25 min read intermediate 3 objectives

Status

Not started

What you will learn

  • Cache dependencies
  • Store and version artifacts
  • Promote artifacts across envs

New to this? Start here

The basics, in plain English

When a pipeline builds your code, the finished result is called an artifact. Storing it and caching repeated work makes pipelines faster and means you deploy exactly what you tested.

Artifact
The packaged output of a build, like a container image or a zip file, ready to deploy.
Artifact store
A place that keeps built artifacts so they can be reused and deployed later.
Cache
Saved results of slow steps (like downloads) so the next run skips them.
Build once
The habit of building a thing one time and promoting that same artifact through environments.
Reproducibility
Getting the same artifact from the same code every time, with no surprises.
01

Build once

Cache package installs to cut minutes. Build an artifact once and promote the same one through environments rather than rebuilding.

Finished this topic?

Mark it done to earn 100 XP and keep your streak alive.