liveBook · Manning

Deployment pipeline

As explained in Think Like a Software Engineering Manager

Continuous delivery is a software delivery practice in which changes are kept in a releasable state and delivered frequently through an automated, repeatable process.

A deployment pipeline supports continuous delivery: changes stay in a releasable state and move to customers frequently through an automated, repeatable process. Delivery works as a cycle: set expectations, deliver a portion of the product, gather feedback, and adjust the next expectations. section 10.1.5 section 11.1.3

Plan for the work that continues after deployment:

  • Monitor service health and alert the on-call team promptly. section 10.1.5
  • Define service-level agreements and prepare troubleshooting runbooks for common customer problems. section 10.1.5
  • Plan infrastructure resources and maintain documentation, especially when enhancing legacy services. section 10.1.5

A first production deployment

If Bob is carrying out a production deployment for the first time and lacks confidence, Alice can arrange for a teammate to shadow him. The support reduces risk while giving Bob a chance to learn. section 11.1.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Describes the delivery cycle and operational responsibilities but does not detail pipeline implementation.
Examples
Uses a first production deployment with a teammate shadowing, plus iterative delivery and customer feedback.
What you can do after
Understand how iterative delivery and production support contribute to a continuing flow of customer value.
How it connects
Connects continuous delivery with agile development, customer feedback, production support, and risk mitigation.

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 Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.