B. Blue Green a software delivery tutorial
Vol. I § Zero-downtime series § A series for junior developers
Zero-downtime delivery · 8 / 10 ·

GitHub Actions runs the playbook

CI builds the image, pushes the registry, then calls ansible-playbook. The GitLab CI file uses the same commands.

This lab has no separate queue panel. GitHub Actions, or the GitLab CI file beside it, runs the same commands.

The command that repeats

ansible-playbook examples/titikterang/ansible/deploy.yml \
  -e image_tag=v1.2.4-dev

image_tag always arrives through -e. It is not written into the playbook.

Slot playground · pipeline
gitbuildregistryplaybook
A git push starts the path.
  1. A git push starts the path.
  2. The base image, then the app image, is built.
  3. The image is pushed to registry.titikterang.local:5000.
  4. CI runs ansible-playbook against the idle slot.

examples/titikterang/.github/workflows/deploy.yml and examples/titikterang/.gitlab-ci.yml mirror each other: build the base, build the app, push, deploy.

Reader notes

Chapter discussion appears once Giscus is connected to the site repository.