Pipelines often end up in a long and slow sequence of activities, but they don’t have to. In this video, see that different types of changes can require different sets of activities in the pipeline.
- [Instructor] As we evolve and flesh out … our walking skeleton pipeline … and release criteria … and we also map all release activities in the pipeline. … What we end up putting an extremely long … and slow path to production? … And the answer is yes. … Even if we automate as much as possible, … it will likely still take a considerable amount of time. … We need smarter pipelines, … not in an artificial intelligence way, … but by thinking more carefully … about our pipeline design … and how can it provide us … not only adequate release confidence, … but also faster feedback … and the shortest path to production possible. … When all activities are serialized, … meaning each activity can only start … when the previous has been completed … and all activities in the pipeline … must be performed for all changes, … then the execution time will grow endlessly … even if we don't add more activities … as the application grows over time. … So will to build test review and other activities. … This is the time to think about making our pipelines short …
In this course, instructor Manuel Pais shows leaders how to rethink CD in their organization to boost the speed and safety of their delivery workflow. Manuel explains why true continuous delivery is an organizational capability, and why software releases should be treated as business decisions. Plus, learn how to define a single path to production that balances speed and reliability; extract and transform data to enable faster release decisions; improve key metrics for high performance sustainably; and more.