Schematex
flowchart·ISO 5807:1985·saas, devops·complexity 3/3

CI/CD pipeline with gated deploy

Flowchart of a trunk-based CI/CD pipeline — build, test, security scan, staging gate, and production deploy with automatic rollback on failed smoke tests.

For the platform engineer

Open in Playground →
flowchart·§ —
↘ preview
100%
Flowchart Flowchart with 14 nodes and 16 edges. commit → build build → unit unit → fail: No No unit → scan: Yes Yes scan → vuln vuln → fail: Yes Yes vuln → stage: No No stage → smoke smoke → fail: No No smoke → approve: Yes Yes approve → wait: No No approve → prod: Yes Yes prod → health health → done: Yes Yes health → rollback: No No rollback → done Push to main Push to main Build artifact Build artifact Unit tests pass? Unit tests pass? Security scan Security scan High-severity CVEs? High-severity CVEs? Deploy to staging Deploy to staging Smoke tests green? Smoke tests green? Fail build Fail build Manual approval? Manual approval? Await approver Await approver Deploy to production Deploy to production Post-deploy health check? Post-deploy health check? Automatic rollback Automatic rollback Release complete Release complete
UTF-8 · LF · 17 lines · 609 chars✓ parsed·13.5 ms·14.5 KB SVG

Scenario

A platform engineer is documenting the team's trunk-based pipeline for a new-hire runbook. The diagram makes the four automated gates (tests → scan → smoke → post-deploy health) and the single human gate (manual approval) obvious at a glance, and shows that every failure path terminates the pipeline rather than silently continuing.

Annotation key

How to read

Start at Push to main. Every diamond is a gate — a No on any of unit tests, CVE scan, or smoke tests terminates at Fail build. Manual approval is the only human gate; it can park the pipeline at Await approver without failing. The post-deploy health check guards production: a failure triggers automatic rollback, which still completes at Release complete because the rollback itself is a successful outcome.

Flowchart syntax →