Design a CI/CD pipeline that automates building, testing, and deploying your application with proper environments, gates, and rollback strategies.
Paste into any LLM. Describe your deployment setup. Use the guide to build or improve your pipeline for faster, safer releases.
You are a DevOps engineer who has built CI/CD pipelines for teams deploying 10-100 times per day, achieving zero-downtime deployments with automated rollbacks and comprehensive quality gates. [APPLICATION TYPE]: Web app / API / Mobile / Microservices [TECH STACK]: Languages, frameworks, and infrastructure [HOSTING]: AWS / GCP / Azure / Vercel / Heroku / Other [CURRENT PIPELINE]: What you have now (if anything) [DEPLOYMENT FREQUENCY]: How often you want to deploy [TEAM SIZE]: Number of developers [ENVIRONMENTS]: Current environments (dev, staging, prod, etc.) Design a comprehensive CI/CD pipeline: **1. Pipeline Architecture** - Pipeline stages and execution order - Trigger conditions (push, PR, merge, manual) - Parallel vs. sequential stage design - Pipeline-as-code structure - Environment variable and secret management **2. Build Stage** - Dependency caching strategy - Build optimization (incremental builds, Docker layer caching) - Artifact management and versioning - Multi-environment build configuration - Build matrix for multiple platforms/versions **3. Quality Gates** - Automated linting and formatting checks - Unit test execution and coverage thresholds - Integration test suite - Security scanning (SAST, dependency audit) - Code quality metrics (complexity, duplication) - Performance benchmark tests - Gate failure handling and notifications **4. Deployment Strategy** - Environment progression (dev -> staging -> production) - Deployment methods: blue-green, canary, rolling - Database migration handling during deployment - Feature flags for safe releases - Smoke tests post-deployment - Automated rollback triggers and procedures **5. Environment Management** - Environment configuration and parity - Preview/ephemeral environments for PRs - Data management across environments - Infrastructure-as-code integration - Environment cleanup and cost management **6. Monitoring and Observability** - Deployment tracking and changelog - Post-deployment health checks - Error rate monitoring after releases - Performance regression detection - Pipeline metrics: build time, success rate, deploy frequency - Alerting and incident response integration