←  All terms
D
QA & Deployment

Deployment

A deployment moves a tested version of code or configuration into a target environment.

A deployment moves a tested version of code or configuration into a target environment. Automated checks speed up validation but do not replace focused manual testing of critical user journeys. The concept is closely related to CI/CD and Staging Environment.

Read more

CI/CD

Staging Environment

Rollback

Git

FAQ

Deployment

When does automating deployments pay off?
It pays off with frequent changes and several contributors. CI/CD replaces error-prone manual steps with repeatable flows. For a rarely changed site, a written checklist can be enough, since building a pipeline itself takes effort and upkeep. Change frequency is the deciding factor, not the wish to look modern.
What should be verified before a deployment?
Before going live, tests on a staging environment should have passed and the scope of changes should be known. A current backup, named owners, and ready monitoring add to that. Critical user journeys deserve a manual look even when automated checks are green, because automation covers only what someone described beforehand.
Why does every deployment need a rollback plan?
Because errors may only become visible in production, and a fast way back limits the damage. Database changes that cannot simply be reversed make this harder. A rollback therefore needs to be planned and rehearsed in advance. An untested way back does not count as one when it matters.
What deployment strategies exist in practice?
Common ones are big bang, rolling, blue-green, and canary. A big bang replaces everything at once. Blue-green keeps two parallel environments and switches between them. Canary first routes only a small share of traffic to the new version. The higher the risk of a failure, the more a staged approach is worth.
How do deployment and release differ?
A deployment technically moves code into an environment, while a release makes a feature available to users. The two do not have to happen at the same time. Feature flags allow code to ship without being switched on. This separation lowers risk, since the technical transfer can happen early and the business release in a controlled way.