Skip to content
Card over a photo showing the CI/CD pipeline diagram, with build, tests, security scan, registry, staging, approval and production stages.

CI/CD Pipeline Diagram

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
5
Difficulty
Intermediate
Updated
November 8, 2026

Every slide (5)

Overview

A developer pushes to a branch and opens a pull request, and merging to main starts the pipeline. The build stage creates one container image tagged with the commit SHA. Unit and integration tests run against that image, and the security stage scans dependencies, the image and the repository for secrets. The signed image is pushed to the artifact registry, where its tag cannot be overwritten. Staging then deploys that same image, and production follows only after a release manager approves it.

Build once and promote the same image, so production runs exactly what staging tested. Keep the approval gate on production only, which keeps staging fast for developers. Production rolls out in batches of 25 percent, and the health checks watch error rate and latency for ten minutes. Swap the generic boxes for your own source control, runner and deploy tools, and the stage order can stay as it is.

Useful for

  • Releasing a web app with an approval step before production
  • Enforcing signed, immutable images for regulated software teams
  • Adding automatic rollback to a rolling deploy on Kubernetes

What's included

  • A designed cover slide
  • The diagram: 10 components and 9 connections as editable shapes
  • A components table and the 8-step data flow
  • A legend with notes
  • The same diagram as a draw.io (diagrams.net) file

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Rename Developer, Commit and pull request, Build and the other boxes inside Continuous integration to your own components, and delete the ones your system does not have.

  3. 3

    Rewrite the 8-step data flow and the 8-row components table so they match the arrows you keep.

  4. 4

    For the draw.io version, download ci-cd-pipeline-diagram.drawio and open it at app.diagrams.net.

What you need

Requirements

  • A Google account for Google Slides, or the free draw.io (diagrams.net) editor

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)
  • draw.io / diagrams.net (.drawio file)

Questions

Why build the image once and promote it instead of rebuilding for production?

Rebuilding can pull in different dependencies or base image versions, so production would run code that was never tested. Promoting the same signed image keeps the artefact identical from staging to production. The image digest is also recorded in the approval log.

What makes a registry tag immutable?

An immutable tag cannot be re-pointed to a different image once it is pushed. A rebuild that tries to reuse the tag is rejected when immutability is enabled, so each tag always refers to the same build. Pin deployments to tags or digests to keep that guarantee.

Why use a rolling update instead of replacing every instance at once?

A rolling update replaces instances a few at a time, so most capacity keeps serving while new ones start. If health checks fail, the rollout stops and the previous image can be redeployed. Updating everything at once removes that safety margin.

  • #infrastructure-diagram
  • #architecture-diagram
  • #google-slides
  • #drawio
  • #diagram-template
  • #free-template

More infrastructure diagram templates

See all 9

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…