CI/CD Pipeline — Architecture Documentation

CI/CD Pipeline

Jenkins build jobs per service, Maven prod packaging, PM2 process management, health-check gating and the UAT → production deployment flow.

Diagram v1.2 · Updated 04 Aug 2026, 08:10 GST— Jenkins job list, Maven prod packaging, PM2 runtime and health gating captured as-is.

100%

Rendering diagram…

Scroll to zoom · drag to pan

1 · Step-by-step workflow

01

Commit triggers Jenkins

BUILD_GATEWAY, BUILD_BACKEND, BUILD_STORE and BUILD_COMMERCE run per Java module.
BUILD_INTEGRATION remains defined but is defunct.

02

Maven packages the services

./mvnw -Pprod produces the production jars for each service.

03

Vite builds the frontend

The TanStack Start app is built and its output published for Nginx to serve.

04

DEPLOY_UAT promotes the build

Artifacts are shipped to the UAT host and the services restarted.

05

PM2 supervises runtime

PM2 manages the process lifecycle and restarts on failure.

06

Health checks gate the release

/management/health liveness and readiness probes verify each service before traffic is accepted.
Production validators fail fast on missing secrets.

2 · Additional details

01

Tooling

Jenkins for build and deploy jobs; Maven wrapper with the prod profile.
Vite for the frontend build; PM2 for process management; Nginx at the edge.
Docker Compose is used for local infrastructure only.

02

Environments

UAT is promoted through DEPLOY_UAT; production follows the same artifact.
Single-host deployment — no load balancer or Kubernetes in Phase 1.

03

Configuration

Consul distributes shared service configuration.
CatalogProductionValidator and GatewayProductionValidator fail fast on missing prod secrets.

04

Known discrepancies

Deploy scripts still reference the deleted integration service.

3 · Advantages & usage

Advantage

A failure in one service does not block the others.
Build times stay short and attributable.

Usage

Four active jobs cover gateway, backend, store and commerce.

4 · Phase 2 additions

01

Automated test and security gates

Add unit, API and SAST stages to the pipeline before promotion.

02

Blue-green or rolling deploys

Remove the restart gap once a second host or load balancer exists.

03

Container orchestration

Containerise the services and adopt orchestration when scale requires it.