Express.js CI/CD Pipelines — Production-Grade Deployment for the Web's Most Popular Framework

Express's flexibility is a double-edged sword for deployment. There is no express deploy command, no standard migration tool, and no official Docker image. Every team builds their own deployment process, and most of them have gaps — missing health checks, no graceful shutdown, environment variables hardcoded in code, and tests that only run locally.

Express applications often grow organically, adding middleware, route files, database connections, and background tasks over time. Without a CI pipeline enforcing quality standards, code quality drifts. ESLint rules get ignored, tests stop being written, and type safety erodes (if TypeScript was even adopted in the first place).

Graceful shutdown is particularly important for Express and almost always overlooked. When your container runtime sends SIGTERM, Express needs to stop accepting new connections, finish processing in-flight requests, close database pools, and then exit. Without this, every deployment drops requests.

We structure the pipeline around three guarantees: code quality, correctness, and safe deployment. Code quality is enforced with ESLint (or Biome for speed), Prettier, and optional TypeScript type checking. These run as the first pipeline stage and fail fast on violations.

Testing uses Jest or Vitest with Supertest for HTTP endpoint testing. We configure a test database (PostgreSQL, MongoDB) as a service container and run your migration tool (Knex, Sequelize, Prisma, or Mongoose) before tests execute. Integration tests hit real endpoints with real database queries. We split tests by speed: fast unit tests run first, slower integration tests run in parallel.

The Docker build produces a minimal image using node:20-alpine. We add a proper SIGTERM handler to your Express app that calls server.close() and waits for connections to drain. The container includes a /healthz endpoint that checks database and cache connectivity. Deployments use rolling updates with the health endpoint as the readiness probe, ensuring no traffic reaches the new version until it is fully ready.

An Express.js CI/CD pipeline:

• Code quality enforcement — ESLint, Prettier, optional TypeScript checks
• Test automation — Jest/Vitest with Supertest and real database services
• Graceful shutdown — SIGTERM handler with connection draining configured
• Health check endpoint — /healthz checking database and external service connectivity
• Docker optimization — alpine base, non-root user, multi-stage build
• Database migrations — automated pre-deploy with your ORM of choice
• Zero-downtime deployment — rolling updates with readiness probe validation