Automated CI/CD Pipelines with GitHub Actions and Docker: A Production DevOps Blueprint

In high-performing engineering teams, deploying software to production is a boring, routine non-event executed multiple times a day—not an anxious Friday night ordeal. Achieving this operational maturity requires Continuous Integration and Continuous Deployment (CI/CD) pipelines that automatically test, build, containerize, and deploy code on every Git push. This handbook walks through architecting enterprise GitHub Actions pipelines with zero-downtime blue/green deployments.

The 4 Pillars of a Robust CI/CD Pipeline

A modern deployment pipeline consists of distinct automated gates that prevent defective code from ever reaching end users:

1. Static Analysis & Linting: Verifying code formatting, TypeScript types, and running static security scanners (ESLint, Prettier, SonarQube, Semgrep).
2. Automated Test Suites: Executing fast in-memory unit tests and integration tests against isolated PostgreSQL/Redis test containers via Docker service containers.
3. Artifact Compilation & Containerization: Building lean Docker images with BuildKit caching, pushing signed images to Amazon ECR or GitHub Container Registry.
4. Automated Deployment & Health Verification: Executing rolling zero-downtime cutovers and rolling back instantly if healthcheck endpoints return non-200 HTTP statuses.

Optimizing GitHub Actions: Docker BuildKit Layer Caching

Building Docker images from scratch on every pull request burns developer time and CI runner minutes. By leveraging GitHub Actions Cache with Docker BuildKit, unchanged dependencies (like node_modules) build in seconds instead of minutes:

# .github/workflows/production-pipeline.yml
name: Production Release Pipeline

on:
  push:
    branches: [main]

jobs:
  test:
    name: Unit & Integration Tests
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:16-alpine
        env:
          POSTGRES_DB: test_db
          POSTGRES_PASSWORD: test_password
        ports:
          - 5432:5432
        options: >-
          --health-cmd pg_isready
          --health-interval 10s
          --health-timeout 5s
          --health-retries 5

    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22
          cache: 'npm'
      - run: npm ci
      - run: npm run lint
      - run: npm run test:ci
        env:
          DATABASE_URL: postgresql://postgres:test_password@localhost:5432/test_db

  build-and-deploy:
    name: Build Docker & Zero-Downtime Deploy
    needs: test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      - name: Log in to Container Registry
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: Build and Push Docker Image with Cache
        uses: docker/build-push-action@v5
        with:
          context: .
          push: true
          tags: ghcr.io/nitaiitsolution/web-app:${{ github.sha }}
          cache-from: type=gha
          cache-to: type=gha,mode=max

      - name: Trigger Rolling Deployment via Webhook
        run: |
          curl -X POST https://deploy.nitaiitsolution.in/webhook/deploy \
            -H "Authorization: Bearer ${{ secrets.DEPLOY_SECRET }}" \
            -d '{"image_tag": "${{ github.sha }}"}'

Frequently Asked Questions