←  All terms
C
QA & Deployment

CI/CD

CI/CD automates code integration, testing, and delivery so changes can be released more frequently and reliably.

CI/CD automates code integration, testing, and delivery so changes can be released more frequently and reliably. Automated checks speed up validation but do not replace focused manual testing of critical user journeys. The concept is closely related to Git and Deployment.

Read more

Git

Deployment

Rollback

FAQ

CI/CD

What typically belongs in a CI/CD pipeline?
Typical stages are build, linting, unit and integration tests, security and dependency checks, automated accessibility checks, and deployment to a preview environment. Critical user journeys still need manual testing on top. Overly long pipelines get bypassed, so fast checks should run first.
When does CI/CD pay off for website projects?
CI/CD pays off once several people work on the code, releases are frequent, or errors in production become costly. Setup takes time up front for pipelines and tests. For a rarely changed site with a single maintainer, a manual process can be enough.
How do continuous integration, delivery, and deployment differ?
Continuous integration merges code changes regularly and checks them automatically through builds and tests. Continuous delivery keeps every verified state releasable, while continuous deployment also publishes it automatically. Whether release approval is manual or fully automatic is a risk decision.