Fast Production Deploy

Skip the full environment chain (dev → qa → uat → staging) and deploy directly to production from the develop branch. Useful when the code has already been validated in lower environments and you need a quick production push.

When to Use

• Redeploy after a reverted rollback — lower envs are already on the correct version
• Config-only changes — environment variable updates that just need a container restart
• Time-sensitive fixes — code is validated but the normal chain would take too long
• Recovering from a cancelled pipeline — changes were deployed to lower envs but prod was missed

caution

This bypasses all lower environment gates and approvals. Only use when you're confident the code on develop is production-ready.

How to Run

1. Open Run Pipeline

Navigate to Build > Pipelines in the left sidebar, then click Run pipeline (top right).

2. Configure the Pipeline

Field	Value
Run for branch name or tag	develop
Variable key	FAST_PROD_PIPELINE
Variable value	true

Click Add variable to add the variable, then click Run pipeline.

3. What Happens

The pipeline starts with most of the normal env chain suppressed:

Suppressed jobs: deploy-dev, deploy-qa, deploy-uat, deploy-staging, deploy-prod, run-migrations-dev, run-seed-dev

Active jobs: build-vault → deploy-prod-fast → run-migrations-prod / run-seed-prod / sync-to-main

4. Deploy

1. Wait for build-vault to complete (rebuilds .env.vault from dotenv.org)
2. Click Play on deploy-prod-fast
3. Approve the protected environment prompt (requires tech lead + PM approval)
4. All 3 production apps deploy in parallel:
   • prod-fastlane-portal
   • prod-fastlane-admin
   • prod-fastlane-api-gateway

5. Post-Deploy

Job	Behavior
run-migrations-prod	Runs automatically if prisma/ files changed in the commit. Force with FORCE_RUN_MIGRATIONS=true.
run-seed-prod	Manual — click Play if you need to reseed production
sync-to-main	Runs automatically — syncs develop to main

Comparison with Normal Pipeline

	Normal Pipeline	Fast Prod Pipeline
Trigger	Push to develop	Web UI with FAST_PROD_PIPELINE=true
Environments	dev → qa → uat → staging → prod	prod only
Approval gates	Each env has its own gate	Production gate only
Apps deployed	3 core apps through the promotion lane	3 production apps only
Time to prod	Hours (manual gates at each env)	Minutes (single gate)

Troubleshooting

Normal env chain jobs still appearing

Make sure you added the variable correctly: key must be exactly FAST_PROD_PIPELINE and value must be true. The pipeline source must be web (Run pipeline button), not a push.

deploy-prod-fast not showing up

The job only appears when all three conditions are met:

1. Pipeline source is web (triggered via Run pipeline)
2. FAST_PROD_PIPELINE variable is set to true
3. Branch is develop