This playbook defines best practices, reusable workflows, and optimization strategies for establishing Continuous Integration and Continuous Deployment (CI/CD) pipelines.

1. Core Execution Phases

Every enterprise CI/CD pipeline should implement the following stages in sequence:

A. Static Analysis & Linting

Run syntax checkers, style linters, and static type verifiers (e.g., Flake8, Ruff, ESLint, mypy).
Fail fast at this stage to prevent expensive test runs on poorly formatted code.

B. Unit & Integration Testing

Execute test suites automatically on every commit, pull request, and merge.
Ensure that the execution runs in a isolated sandbox environment (e.g. docker or virtual environment).

C. Build & Packaging

Build production assets, container images, or binaries.
Ensure builds are deterministic and reproducible.

D. Security Scanning

Run SAST (Static Application Security Testing) and dependency auditing tools (e.g., npm audit, pip-audit, Trivy, Bandit).

2. Speeding Up Pipelines with Caching

Pipeline execution time directly impacts developer velocity. Always implement dependency caching.

A. GitHub Actions Caching Patterns

Node.js/npm: Cache ~/.npm and node_modules.

Python/pip: Cache pip download cache and poetry virtual environments.

- name: Set up Python
  uses: actions/setup-python@v4
  with:
    python-version: '3.10'
    cache: 'pip' # built-in pip caching

3. Configuration Best Practices

Never Commit Secrets: Never hardcode private keys, passwords, or cloud credentials in pipeline configurations. Always reference secrets from your platform's secure vault (e.g. ${{ secrets.GITHUB_TOKEN }}).
Environment Parity: Ensure that CI commands can be run locally using a local shell wrapper or script (e.g., ./helper.sh validate or npm run test).
Strict Pull Request Gates: Enforce branch protection rules requiring status checks (linting, tests, build) to pass before a pull request can be merged.

Más de este repositorio

mismo repositorio

task-management

rafaelghif/antigravity-agents

Playbook for capturing design alignment from /grill-me, generating issue specifications, and managing task boards.

2026-07-112

skill-evolution

rafaelghif/antigravity-agents

Playbook instructing agents how to dynamically formulate, design, bootstrap, and register new workspace skills when facing skill gaps.

2026-07-092

conversational-agent

rafaelghif/antigravity-agents

Playbook for translating natural language requests about tasks, profiles, locking, and validation into CLI helper executions.

2026-07-022

database-evolution

rafaelghif/antigravity-agents

Playbook for writing safe database migrations, managing schema evolutions, executing reversible rollbacks, and avoiding table lock contention in enterprise environments.

2026-07-022

performance-optimization

rafaelghif/antigravity-agents

Guidelines for CPU profiling, identifying database query bottlenecks (N+1 queries), diagnosing memory leaks, and optimizing resource execution speeds.

2026-07-022

release-management

rafaelghif/antigravity-agents

Guidelines for containerization (Dockerfile best practices), release versioning, blue-green deployment, feature flag rollouts, and post-deployment smoke verification.

2026-07-022

name	ci-cd
description	Playbook for setting up CI/CD pipelines, automating linting, testing, building, caching, and staging release gates.

CI/CD Pipelines Playbook

This playbook defines best practices, reusable workflows, and optimization strategies for establishing Continuous Integration and Continuous Deployment (CI/CD) pipelines.

1. Core Execution Phases

Every enterprise CI/CD pipeline should implement the following stages in sequence:

A. Static Analysis & Linting

Run syntax checkers, style linters, and static type verifiers (e.g., Flake8, Ruff, ESLint, mypy).
Fail fast at this stage to prevent expensive test runs on poorly formatted code.

B. Unit & Integration Testing

Execute test suites automatically on every commit, pull request, and merge.
Ensure that the execution runs in a isolated sandbox environment (e.g. docker or virtual environment).

C. Build & Packaging

Build production assets, container images, or binaries.
Ensure builds are deterministic and reproducible.

D. Security Scanning

Run SAST (Static Application Security Testing) and dependency auditing tools (e.g., npm audit, pip-audit, Trivy, Bandit).

2. Speeding Up Pipelines with Caching

Pipeline execution time directly impacts developer velocity. Always implement dependency caching.

A. GitHub Actions Caching Patterns

Node.js/npm: Cache ~/.npm and node_modules.

Python/pip: Cache pip download cache and poetry virtual environments.

- name: Set up Python
  uses: actions/setup-python@v4
  with:
    python-version: '3.10'
    cache: 'pip' # built-in pip caching

3. Configuration Best Practices

Never Commit Secrets: Never hardcode private keys, passwords, or cloud credentials in pipeline configurations. Always reference secrets from your platform's secure vault (e.g. ${{ secrets.GITHUB_TOKEN }}).
Environment Parity: Ensure that CI commands can be run locally using a local shell wrapper or script (e.g., ./helper.sh validate or npm run test).
Strict Pull Request Gates: Enforce branch protection rules requiring status checks (linting, tests, build) to pass before a pull request can be merged.