ci-cd-pipeline-architecturelisted

# CI/CD Pipeline Architecture ## Purpose Pipelines are the line between "works on my machine" and "production is down." This skill ensures code is built exactly once, tested comprehensively, and deployed reliably through immutable artifacts without human intervention. ## When to use - Setting up a new GitHub Actions, GitLab CI, or Jenkins workflow - Automating manual deployment processes - Enforcing code quality checks on Pull Requests - Establishing environment promotion strategy (dev → staging → production) ## When NOT to use - Local development builds (use Makefile or npm scripts) - Manual hotfixes (always use pipeline) ## Inputs required - Git repository with configured CI/CD platform (GitHub Actions, GitLab CI, Jenkins) - Build/test environment specifications - Environment configurations (dev, staging, prod) - Secret management platform access ## Workflow 1. **Trigger Definition**: Define strict triggers. Run tests/linters on `pull_request`. Run builds/deployments on `push` to `main` or upon `release` tags. 2. **Fail Fast**: Order jobs sequentially by speed. Run Linters, Type Checkers first. If they fail, halt before running expensive test suites. 3. **Automate Testing**: Run unit and integration tests inside isolated, ephemeral containers (e.g., Docker). 4. **Build Immutable Artifacts**: Compile code or build Docker image exactly ONCE. Tag the artifact with the Git commit SHA. 5. **Promote the Artifact**: Deploy the EXACT SAME artifact from Staging to Production. D