Pipelines
The S0PMOBAI program uses reusable Azure DevOps templates to deliver both the web UI and backend API through canary-driven releases. Use the summaries below to jump directly to the detailed pipeline documentation.
| Pipeline | Summary |
|---|---|
| UI Build & Canary Pipeline | Builds the s0pmobai-admin-site React UI, publishes a reusable artifact, and promotes it across Dev → Test → Stage → Prod with canary health checks. |
| WebAPI Build & Canary Pipeline | Compiles the Publix.S0PMOBAI.WebAPI service, runs multi-region canary deployments, and manages slot promotions for safe production rollouts. |
| Database Build & Deploy Pipeline | Builds the S0PMOBAI.sqlproj, packages the DACPAC, and pushes schema changes through Dev → Test → Stage → Prod using azure-pipelines.db.build-and-deploy.yml. |
Key Concepts
- Shared Templates: Both pipelines import versioned templates from
S0AIDXXX-AI Delivery/s0aidxxx-templatesto enforce consistent build and deployment practices. - Canary Rollouts: Deployments start in a canary slot or subset of infrastructure, validate health, then promote to the primary slot when checks pass.
- Environment Guards: Release branches can bypass lower environments while still allowing direct production deployments when required.
- Configuration via Parameters: Runtime settings, regions, and build parameters are supplied through template inputs so teams can evolve environments without rewriting pipeline logic.
- Database Automation: The database pipeline reuses the same template library to gate DACPAC deployments with environment-specific service connections and approvals.