liveBook · Manning

Deployment pipeline

As explained in Grokking Software Architecture

An automated sequence of stages that builds, tests, and moves software changes toward deployment.

A deployment pipeline is an automated conveyor belt that builds, checks, and moves software changes toward production. Instead of relying on someone to copy files to a server at 2:00 AM, it makes deployment a repeatable part of the architecture. section 13.2 section 13.5

A practical pipeline puts changes through stages rather than sending them straight into production:

  • Verify the change with automated checks, such as linting, security scans, unit tests, and architectural boundary tests. section 13.5
  • Build an immutable artifact: a fixed package of the verified software that can move down the line. section 13.5
  • Promote the artifact progressively through environments, so it earns trust before reaching active production pools. section 13.6
  • Release safely, coordinating traffic and health checks where the infrastructure requires them. section 13.2

The conveyor belt’s shape depends on what it carries. A monolith can produce one build artifact, but a cluster still needs coordinated rolling upgrades. Microservices add independent release schedules and backward-compatible API contracts. Multiple database engines can also require separate migration, validation, and reindexing workflows. section 13.2 section 8.2.7

Listing 13.2 GitHub Actions Delivery Pipeline Blueprint
name: Order Service Lifecycle Pipeline
 
on:
  push:
    branches: [ "main" ]      #A
  pull_request:
    branches: [ "main" ]
 
jobs:
  verify-and-build:
    runs-on: ubuntu-latest    #B
 
    steps:
    - name: Checkout Source Code
      uses: actions/checkout@v4
 
    - name: Setup .NET SDK Runtime
      uses: actions/setup-dotnet@v4
      with:
        dotnet-version: '10.0.x'
 
    - name: Restore Package Cache Dependencies
      run: dotnet restore
 
    - name: Execute Logic & Architecture Test Suites
      run: dotnet test --no-restore --configuration Release    #C
 
    - name: Login to Secure Container Registry
      if: github.event_name == 'push' && github.ref == 'refs/heads/main'
      uses: docker/login-action@v3
      with:
        registry: registry.shopzilla.com
        username: ${{ secrets.REGISTRY_USERNAME }}    #D
        password: ${{ secrets.REGISTRY_PASSWORD }}
 
    - name: Bake and Push Immutable Container Artifact
      if: github.event_name == 'push' && github.ref == 'refs/heads/main'
      uses: docker/build-push-action@v5
      with:
        context: .
        file: ./ShopZilla.OrderService/Dockerfile
        push: true
        tags: |
          registry.shopzilla.com/order-service:latest 
          registry.shopzilla.com/order-service:${{ github.sha }}    #E

This GitHub Actions configuration shows pipeline rules as code: it checks out a change, sets up .NET, restores dependencies, and runs tests. Focus on the stage-gate structure rather than memorizing YAML syntax. section 13.6

A clean delivery is not the same as a healthy running system. After deployment, logs, metrics, and distributed tracing help reveal runtime faults and network problems that the pipeline alone cannot see. section 13.10.3

How Grokking Software Architecture covers it

How deep it goes
Explains verification, artifact building, promotion, and release sequencing, with a configuration example that emphasizes stage-gate logic over syntax.
Examples
Uses an order-service workflow and a blueprint exercise to illustrate verification, environment promotion, and release design.
What you can do after
Evaluate a deployment design for automated checks, progressive promotion, and infrastructure-specific release coordination.
How it connects
Connects deployment pipelines to immutable infrastructure, rolling upgrades, API compatibility, and observability.

Also explained in

Compare how 37 books explain deployment pipeline →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.