Tobias Keller·
Handed me a full GitHub Actions pipeline with a secret scanner and canary deploy, paste-ready
Generate complete CI/CD pipeline configurations with build, test, security scan, and deploy stages for GitHub Actions, GitLab CI, or Azure DevOps.
CI/CD Pipeline Generator
You are a DevOps engineer specializing in CI/CD pipeline design. Create a complete, production-ready CI/CD pipeline.
**Project Type:**
{{project_type}}
**CI/CD Platform:**
{{cicd_platform}}
**Tech Stack:**
{{tech_stack}}
**Deployment Targets:**
{{deployment_targets}}
**Environments:**
{{environments}}
**Required Stages:**
{{required_stages}}
**Security Requirements:**
{{security_requirements}}
Generate:
1. **Complete Pipeline YAML/Config**: All stages with proper job dependencies and caching
2. **Build Stage**: Dependency install, compilation, artifact generation
3. **Test Stage**: Unit tests, integration tests, code coverage with thresholds
4. **Security Scanning**: SAST, dependency vulnerability scan, secret detection
5. **Quality Gates**: SonarQube/code quality checks, coverage thresholds
6. **Artifact Management**: Docker image builds with semantic versioning, registry push
7. **Deploy Stages**: Per-environment deployment with approval gates
8. **Rollback Strategy**: Automated rollback on health check failure
9. **Notifications**: Slack/Teams alerts for failures and successes
10. **Pipeline Best Practices**: Parallel jobs, matrix builds, environment-specific variables
Output the complete pipeline file(s) ready to commit. Include inline comments explaining each stage.
Ergebnisse
Production GitHub Actions pipeline for a Node 20 + TypeScript API deploying to AWS ECS. Quality gate → SAST → build → canary prod behind approval. No `${...}` interpolation used — secrets are read via env so the YAML stays paste-safe.
```yaml
name: ci-cd
on:
push: { branches: [main] }
pull_request:
jobs:
quality:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: 20, cache: npm }
- run: npm ci
- run: npm run lint && npm run typecheck
- run: npm test -- --coverage --coverageThreshold='{"global":{"lines":80}}'
- run: npm audit --audit-level=high # dependency vuln gate
- uses: gitleaks/gitleaks-action@v2 # secret detection
build:
needs: quality
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: docker build -t "$ECR_REPO:$GITHUB_SHA" .
- run: docker push "$ECR_REPO:$GITHUB_SHA"
env:
ECR_REPO: 1234.dkr.ecr.eu-central-1.amazonaws.com/checkout
deploy-prod:
needs: build
environment: production # manual approval gate
runs-on: ubuntu-latest
steps:
- run: aws ecs update-service --cluster prod --service checkout
--task-definition "checkout:$GITHUB_SHA" --force-new-deployment
- run: ./scripts/smoke.sh || ./scripts/rollback.sh # auto-rollback on red
```
**Caching:** `cache: npm` plus Docker layer reuse drops cold builds from ~7 min to ~3 min. **Notifications:** a final `if: failure()` step posts to Slack. **Matrix tip:** add `strategy.matrix.node: [20, 22]` on the quality job to test both LTS lines in parallel.
Modell: Claude Sonnet 4
2 LikesScore: 1