It is beneficial for Agile teams to employ automation to ensure that the state of code and other technical artifacts is healthy, and where deployment of those artifacts is automatically done to one or more target environments. Continuous Deployment implies that there is sufficient infrastructure and instrumentation in place, such that after each successful integration, the deployment target(s) is/are updated. Additional instrumentation helps ensure that if a problem is detected, other actions trigger, such as aborting a deployment, performing a roll-back, and potentially sending alerts that human intervention may be needed.
Continuous Deployment Video
Continuous Deployment Podcasts
Continuous Deployment Example
Authored by Philip Rogers
Photo by Joel Rivera-Camacho on Unsplash
Agile World Resources are provided as free resources to anyone seeking to learn more and are shared under a creative commons attribution license. This means if you use a resource elsewhere you must name Agile World Publishing as the source, who the author is, and the photo creator (if used).