Abstract: Techniques are disclosed for reducing the time needed to deploy updated versions of an application using a deployment pipeline. To do so, a deployment manager may collect statistics reflecting how often any given stage of the deployment pipeline is completed successfully in deploying updates to the application. In cases where a current stage has a sufficient approval percentage, the deployment pipeline may begin deploying an updated version of the application into an environment specified for a subsequent stage of the deployment pipeline, before the current stage of the pipeline is complete. Provided the current stage completes successfully, the subsequent stage can be initiated by activating the pre-deployed versions of the application.

Abstract: Techniques are disclosed for reducing the time needed to deploy updated versions of an application using a deployment pipeline. To do so, a deployment manager may collect statistics reflecting how often any given stage of the deployment pipeline is completed successfully in deploying updates to the application. In cases where a current stage has a sufficient approval percentage, the deployment pipeline may begin deploying an updated version of the application into an environment specified for a subsequent stage of the deployment pipeline, before the current stage of the pipeline is complete. Provided the current stage completes successfully, the subsequent stage can be initiated by activating the pre-deployed versions of the application.

Abstract: Technologies are disclosed herein for automated software release lifecycle management. In particular, a software release management network service is disclosed that provides functionality for allowing a software developer to automate aspects of a software release pipeline. A software release pipeline can have multiple stages, each of which can have multiple actions. The actions can include internal actions that utilize network services internal to a service provider network. The actions can also include external actions that utilize network services that are external to a service provider network. The internal and external actions can perform various release-related functions, such as obtaining source code, building the source code, deploying built program code, and for performing tests. Stage gates and/or action gates can also be defined for conditional execution of the next stage or action in a software release pipeline, respectively. A gate bypass can also be specified to override stage or action gates.