Which stages do I need?
One of the questions that frequently arises when working with releases is, which stages do I need in my release pipeline? According to the documentation, stages should denote the major divisions of a release pipeline. When starting out with releases, this often boils down to having one stage per environment in a release pipeline. Appropriate stages include test, acceptance, and production.
When working with releases for a long time, we might incorporate more automation in the pipelines and want to add extra checking stags to them. An example might be a stage called load test that is executed in parallel to the test stage. Another example might be the introduction of a stage for automated UI tests.
No matter which stages ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access