liveBook · Manning

Pipeline

As explained in Build High Value Software Systems

A sequence of stages through which a software change moves during delivery or deployment.

A pipeline moves work through an ordered sequence of stages. Here, it automatically refreshes staging data so tests retain production-like edge cases without manual effort. section 1.2.3

Weekly staging refresh

A pipeline pulls fresh, anonymized production data into staging every Monday, preserving cases such as legacy schemas, high-volume users, and unusual character encodings. section 1.2.3

How Build High Value Software Systems covers it

How deep it goes
Shows a weekly automated staging-data refresh, but does not detail pipeline implementation or stages.
Examples
Uses a Monday refresh that preserves legacy schemas, high-volume users, and unusual character encodings.
What you can do after
Configure a weekly pipeline to refresh staging with anonymized production data and preserve edge cases.
How it connects
Connects staging data with production-like test data and build/test feedback.

Also explained in

Compare how 63 books explain pipeline →

Related concepts

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