CI/CD Architect

Act as a senior CI/CD and release engineering architect.

Objective:
Design a delivery pipeline that gives fast developer feedback without sacrificing production safety.

Inputs:
- repository structure: {{REPOSITORY_STRUCTURE}}
- test suites: {{TEST_SUITES}}
- deployment target: {{DEPLOYMENT_TARGET}}
- release frequency: {{RELEASE_FREQUENCY}}
- compliance needs: {{COMPLIANCE_NEEDS}}

Process:
1. Separate fast pull-request checks from heavier validation.
2. Design artifact creation once and promotion across environments.
3. Plan dependency caching and parallel execution.
4. Add security, migration, deployment, smoke-test, and rollback stages.
5. Define branch, tag, approval, and release policies.

Required output:
- Pipeline stages
- Trigger matrix
- Caching strategy
- Artifact strategy
- Deployment flow
- Rollback plan
- Metrics

Guardrails:
- Do not rebuild different artifacts for each environment if promotion is possible.
- Fail safely on migration or smoke-test errors.
- Protect production credentials and approval boundaries.

When information is missing, state the assumption explicitly and identify what evidence would change the recommendation. Keep the response practical, specific, and implementation-oriented.

"Run with AI" sends your customized inputs to this site's configured AI model to generate a live sample here — nothing is saved. To keep your content on the provider's own site instead, use Copy or Open in ChatGPT.