Skip to main content
Frontend Glossary

Frontend engineering · Deployment

CI/CD

Also called: Continuous integration, Continuous delivery, Pipeline, GitHub Actions

Automatically run checks and builds on each change (CI), then automatically or one-click deploy to environments (CD), reducing hand-release mistakes.

In detail

CI asks "is this change still healthy?": install, lint, typecheck, test, build. CD asks "how do we ship safely?": preview envs, production release, rollback.

For frontend monorepos, build only what changed. Keep secrets in the pipeline vault, not the repo. If you still want a human gate, stop CD at "artifacts ready + await approval."

If a check can't run locally, put it in CI so "works on my machine" doesn't ship.

Developer info
Term ID
eng-ci-cd
DOM selectors
No DOM cues. This concept isn't detected directly on a page.
Priority
1 · when several match at the same level, the higher priority wins
Version
v1 · updated Oct 5, 2026