ci-cd-expert（CI CD 专家）

CI/CD Expert

Create, debug, and optimize CI/CD pipelines.

Platform Selection

Quick pick:

• GitHub repo? → GitHub Actions
• GitLab repo? → GitLab CI
• Need extreme parallelism? → CircleCI
• Azure/Microsoft shop? → Azure DevOps
• Using Jira/Confluence? → Bitbucket Pipelines

Core Workflows

1. Pipeline Creation

Requirements → Platform Selection → Structure → Implementation → Validation

Steps:

1. Identify triggers (push, PR, schedule, manual)
2. Define stages (build, test, deploy)
3. Map environments (dev, staging, prod)
4. Configure secrets and variables
5. Set up caching strategy
6. Implement deployment gates

Minimal viable pipeline:

# Every pipeline needs these elements
triggers:        # When to run
stages:          # What to run (in order)
  - build        # Compile/bundle
  - test         # Validate
  - deploy       # Ship (optional)
caching:         # Speed optimization
environment:     # Secrets/variables

2. Pipeline Review

Review checklist (in order of priority):

1. Security

- [ ] Secrets not hardcoded - [ ] Minimal permissions (least privilege) - [ ] Dependencies pinned (no @latest) - [ ] Untrusted input sanitized

1. Reliability

- [ ] Idempotent steps - [ ] Explicit failure handling - [ ] Timeouts configured - [ ] Retry logic for flaky steps

1. Efficiency

- [ ] Caching implemented - [ ] Parallelization where possible - [ ] Conditional execution (skip unchanged) - [ ] Resource sizing appropriate

1. Maintainability

- [ ] DRY (reusable workflows/templates) - [ ] Clear naming conventions - [ ] Comments on non-obvious logic

3. Pipeline Debugging

Diagnostic framework:

Symptom → Category → Platform-specific fix

Common failure categories:

Debug approach:

1. Read the full error (scroll up!)
2. Identify which step failed
3. Check if it works locally
4. Add debug output (set -x, verbose flags)
5. Check platform-specific logs

4. Deployment Strategy Selection

                     Risk Tolerance
                          ↑
                    Low   │   High
                          │
        ┌─────────────────┼─────────────────┐
        │                 │                 │
 Slow   │   Blue-Green    │    Rolling      │  Fast
        │   (safest)      │   (balanced)    │
        │                 │                 │
        ├─────────────────┼─────────────────┤
        │                 │                 │
        │    Canary       │   Direct        │
        │   (measured)    │   (fastest)     │
        │                 │                 │
        └─────────────────┴─────────────────┘
                     Rollback Speed →

Decision guide:

5. Build Optimization

Optimization priority:

1. Caching (highest impact)
2. Parallelization
3. Conditional execution
4. Resource sizing
5. Image optimization

Caching hierarchy:

Dependencies (npm, pip) → Build artifacts → Docker layers → Test fixtures
       ↑                        ↑                ↑              ↑
   Always cache          If build slow     If using Docker   If tests slow

Cache key strategies:

# Dependencies - hash lockfile
key: deps-${{ hashFiles('package-lock.json') }}

# Build artifacts - hash source
key: build-${{ hashFiles('src/**') }}

# Combined - hash both
key: ${{ runner.os }}-${{ hashFiles('**/lockfiles') }}

Common Patterns

Secret Management

# ✅ Good: Environment variables
env:
  API_KEY: ${{ secrets.API_KEY }}

# ❌ Bad: Inline secrets
run: curl -H "Authorization: hardcoded-secret"

Secret rotation checklist:

• [ ] Secrets stored in platform secret store
• [ ] Secrets scoped to minimum required (repo/org/env)
• [ ] Rotation procedure documented
• [ ] No secrets in logs (mask sensitive output)

Environment Progression

┌─────────┐    ┌─────────┐    ┌─────────┐    ┌─────────┐
│   Dev   │ →  │Staging  │ →  │   QA    │ →  │  Prod   │
└─────────┘    └─────────┘    └─────────┘    └─────────┘
  Auto          Auto          Manual          Manual
  deploy        deploy        approval        approval

Artifact Management

# Upload
- name: Upload build
  uses: actions/upload-artifact@v4
  with:
    name: dist
    path: dist/
    retention-days: 7

# Download (later job)
- name: Download build
  uses: actions/download-artifact@v4
  with:
    name: dist

Matrix Builds

# Test across multiple versions
strategy:
  matrix:
    node: [18, 20, 22]
    os: [ubuntu-latest, macos-latest]
  fail-fast: false  # Continue other jobs if one fails

Anti-Patterns

❌ Secrets in Logs

# BAD
run: echo "Deploying with key $API_KEY"

# GOOD
run: echo "Deploying..." && deploy --key "$API_KEY"

❌ No Caching

# BAD: Downloads deps every run
- run: npm install

# GOOD: Cache node_modules
- uses: actions/cache@v4
  with:
    path: node_modules
    key: ${{ hashFiles('package-lock.json') }}
- run: npm ci

❌ Mutable Tags

# BAD: Could change anytime
uses: actions/checkout@master

# GOOD: Pinned version
uses: actions/checkout@v4

❌ Overly Broad Triggers

# BAD: Runs on every push to every branch
on: push

# GOOD: Specific triggers
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

❌ Sequential When Parallel Works

# BAD: 15 min total
jobs:
  lint:
    ...
  test:
    needs: lint  # Waits for lint
    ...

# GOOD: 10 min total (parallel)
jobs:
  lint:
    ...
  test:
    ...  # Runs alongside lint

Troubleshooting Quick Reference

Integration Points

With version control:

• Branch protection rules
• Required status checks
• Auto-merge on success

With deployment targets:

• Cloud providers (AWS, GCP, Azure)
• Container registries (Docker Hub, ECR, GCR)
• Kubernetes clusters
• Serverless (Lambda, Cloud Functions)

With monitoring:

• Build metrics (duration, success rate)
• Deployment tracking
• Error alerting (Slack, PagerDuty)

Skill Usage

Creating a pipeline:

1. Identify platform from repo hosting
2. Read platform-specific reference
3. Follow creation workflow above
4. Validate with platform's linter

Debugging a failure:

1. Categorize the error (table above)
2. Read debugging-guide.md for detailed steps
3. Check platform-specific quirks

Implementing deployments:

1. Choose strategy using decision guide
2. Read deployment-strategies.md
3. Implement with platform-specific syntax

Security audit:

1. Use review checklist above
2. Read security-checklist.md for comprehensive review
3. Generate ohno tasks for findings

References:

• references/github-actions.md — GitHub Actions syntax, patterns, marketplace actions
• references/gitlab-ci.md — GitLab CI syntax, Auto DevOps, runners
• references/circleci.md — CircleCI orbs, parallelism, caching
• references/azure-devops.md — Azure Pipelines, templates, stages
• references/bitbucket-pipelines.md — Bitbucket Pipelines, pipes, deployments
• references/deployment-strategies.md — Blue-green, canary, rolling implementations
• references/debugging-guide.md — Platform-specific debugging techniques
• references/security-checklist.md — OWASP CI/CD security, supply chain