Pipelines
Gate, deploy, smoke, health, then promote or roll back — automatically.
A pipeline is an orchestrated deployment: a sequence of stages where each must pass before the next.
gate → deploy → smoke → health → promote
│
└─ fail ──► automatic rollbackStages
| Stage | Does |
|---|---|
| Gate | Pre-conditions: no freeze, approvals present, no open SEV1 |
| Deploy | Runs the deployment |
| Smoke | Runs smoke tests against the deployed version |
| Health | Watches the health window — errors, incidents, rate |
| Promote | Moves to the next environment, or marks it good |
Automatic rollback
If smoke or health fails, the pipeline rolls back without waiting for a human.
Automatic rollback is only safe if your migrations are backwards-compatible for one release. They are — that is a rule, not a hope. See Migrations.
The live console
While a pipeline runs, the console streams each stage's output. You can watch a deploy without opening Jenkins.
Configuration and secrets
Pipelines pull configuration and secrets from Infisical at run time, so a pipeline definition contains no credentials and can be read by anybody.
Notifications
Pipeline events go to Slack: started, stage failed, rolled back, promoted.
Configure the channel in Delivery → Deployments → Setup.
Environment promotion
A pipeline can promote the exact artifact that passed in a lower environment, rather than rebuilding for the next one.
Promote artifacts, do not rebuild. A rebuild is a different binary, and every test that passed in staging tested something that is not what you are about to run in production.
Designing one
Keep gates cheap and smoke tests fast. A pipeline that takes forty minutes is a pipeline people bypass, and a bypassed pipeline protects nothing.
Fast, narrow smoke tests plus a real health window beats an exhaustive suite that nobody waits for.
Where this behaviour lives: backend/internal/service/deploy_orchestrator.go, frontend/src/app/deployments/pipelines/. If the code and this page disagree, the code is right — please fix the page.
Part of Delivery — Deployments, pipelines, releases and everything that ships code.