Continuous deployment automatically sends every production-ready software change to production. Its appeal is clearest when the existing route from commit to release is slow and painful. section 2.1.3
Delivery bottlenecks that make frequent releases difficult include:
- Shared changes can leave the build unreleasable; feature branches can instead lead to lengthy merges and post-sprint stabilization. section 2.1.3
- Complexity can require running the full test suite, manual testing, and days to complete a testing cycle. section 2.1.3
Figure 2.2 A case of outgrowing a monolithic architecture. A large number of FTGO developers commit their changes to a single source code repository. The path from code commit to production is long and arduous and involves manual testing. The FTGO application is large, complex, unreliable, and difficult to maintain.
Shows the long, manually tested path from a shared code repository to production that frequent deployment aims to shorten. section 2.1.3






