liveBook · Manning

Deployment pipeline

As explained in Road to Kubernetes

CI/CD is the practice of continuously integrating code changes and continuously delivering or deploying software through automated pipelines.

A deployment pipeline automates the steps that move code toward production, including testing and configuration. It makes deployment repeatable and can keep project secrets in one place. section 4.0 section 4.1

The pipeline can support different levels of automation:

  • Continuous integration combines code changes into one project and recommends automatically testing them. section 4.1
  • Continuous delivery deploys code to a production-like staging environment for review before release. section 4.1
  • Continuous deployment automatically builds, tests, and deploys code to production without manual approval. section 4.1

Automate a deployment with GitHub Actions

A GitHub Actions workflow can run when repository code changes, run tests, and invoke configuration automation. The same tool can build container images, keeping that work close to the code and its deployment secrets. section 4.0 section 6.1

How Road to Kubernetes covers it

How deep it goes
Defines CI, continuous delivery, and continuous deployment, but leaves automated-test authoring beyond scope.
Examples
Uses GitHub Actions workflows for tests and configuration automation, and compares automated container builds through GitHub Actions or Docker Hub.
What you can do after
Configure GitHub Actions pipelines to run tests and configuration automation, deploy code, and centralize runtime secrets.
How it connects
Connects GitHub Actions with Git, automated testing, staging, Ansible, and container builds.

Also explained in

Compare how 30 books explain deployment pipeline →

Related concepts

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