CI/CD pipeline icons

The 36 icons, described

Buildbuild

A build — turning source code into the artifact that actually runs.

Build passbuild-pass

Build pass — it compiled and the tests agreed, green and successful.

Build failbuild-fail

Build fail — the build broke, red with an error that has to be fixed.

Pipelinepipeline

A pipeline — work moving through stages in order, from data ingestion to a finished output.

Continuous integrationci

Continuous integration — every change built and tested automatically as soon as it lands.

Continuous deliverycd

Continuous delivery — every successful build on its way out to a release.

Deploydeploy

Deploy — ship a build to the place where people will actually use it.

Rolloutrollout

A rollout — to a few users, then more, then everyone, a staged ramp.

Canarycanary

A canary release — one instance running the new version so problems show up early.

Blue-greenblue-green

Blue-green deployment — two identical stacks, one live, swapped over at cutover.

Rollbackrollback

Rollback — put the previous version back after a bad release.

Releaserelease

A release — a version tagged, built and shipped to users as a package.

Artifactartifact

An artifact — what the build produced, the binary, bundle or package to ship.

Registryregistry

A registry — where named, published things live and can be looked up.

Containercontainer

A container — an app packaged with everything it needs, isolated like a Docker image.

Test runtest-run

A test run — the suite is going, tests in progress with results coming in.

Coveragecoverage

Test coverage — how much of the code the tests actually touch, as a percentage.

Reviewreview

Review — another pair of eyes on the change before it lands in the main branch.

Commitgit-commit

A git commit — one change recorded as a snapshot with its own hash.

Branchbranch-git

A git branch — a line of work split off from another so changes can be made in isolation.

Mergegit-merge

A git merge — two lines of work joined back into one branch of history.

Git pull requestgit-pull-request

A branch offered back to the line it came from — a pull request, changes proposed for review.

Lockfilelockfile

A lockfile — the exact versions of every dependency, pinned and resolved.

Hot reloadhot-reload

Hot reload — the app keeps running while the code changes underneath it.

Cache hitcache-hit

A cache hit — found it without asking anyone, served fast from the cache.

Health probehealth-probe

A health probe — the service poked on schedule, and it answered that it is alive.

Monitor checkmonitor-check

A screen with a check on it — the display is fine, the machine reports healthy.

Incidentincident

An incident — something is wrong in production and someone has to respond.

On callon-call

On call — whoever is carrying the pager on the rota right now.

Runbookrunbook

A runbook — the written procedure for what to do when a system breaks.

Alertalert

An alert — something fired, a notification raised or a page sent out.

Loglog

A log — what happened, written down as it happened, entry by entry.

Tracetrace

A trace — one request followed through every service it touched, span by span.

Spanspan-trace

A span — one timed piece of work inside a distributed trace across services.

Scale upscale-up

Scale up — give it more capacity, grow to bigger or more instances.

Scale downscale-down

Scale down — give it less capacity, shrink to smaller or fewer instances.

In code, each is one import — import { Build } from "@iconmind/react/icons/build" — and the same name in Vue, Svelte, Solid, Preact, React Native, Astro, Blade and Flutter.