Every time the pipeline is bypassed to apply a fix in production the risk of regression and inconsistencies increases. Learn how to define a single path to production that balances speed and reliability.
- [Instructor] Having the pipeline as the single channel … to production means that any change, … no matter how small or how urgent, … can only be deployed to a live environment … from the pipeline. … Every time the pipeline is bypassed to apply a fix … directly in production, … we introduce risk of regressions and inconsistencies. … Simply merging the changes into a version control repository … after the fix in production is risky. … We have no guarantee that deploying the application again … from the pipeline with the new code … will have the same end result. … Plus, it's very easy for someone to make a minor change … in the production environment … that they later forget to check in into version control. … This scenario's aggravated when the initial fix … did not actually solve the issue … at that first attempt. … The tendency will be to keep making changes … directly in production until the problem gets solved. … By this point, it becomes hard to trace back … all the changes since they were made …
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.