tomevault-io CI/CD Patterns
Activate this skill when designing or optimizing CI/CD pipelines.
When to Use
- Designing new CI/CD pipelines
- Optimizing build times and caching
- Implementing deployment strategies
- Adding security scanning to pipelines
- Setting up multi-environment promotion
- Configuring GitOps workflows
Pipeline Stages
- Validate: lint, format check, schema validation
- Build: compile, bundle, create artifacts
- Test: unit, integration, contract tests
- Scan: SAST, dependency audit, container scan
- Package: build container image, push to registry
- Deploy: apply to target environment
- Verify: smoke tests, health checks, canary analysis
Deployment Strategies
- Rolling: gradual replacement, zero-downtime
- Blue-Green: instant switch between environments
- Canary: route percentage of traffic to new version
- Feature Flags: deploy dark, enable incrementally
Rules
- Fail fast: cheapest checks run first
- Cache aggressively: dependencies, layers, build artifacts
- Pin versions: actions, base images, dependencies
- Use OIDC: no long-lived credentials in CI
- Separate build from deploy for auditability
- Every deployment must be reversible
- Quality gates must block on failure
- Pipeline changes require code review
Source: ihatesea69/kiro-kit — distributed by TomeVault.