AWS CodePipeline supports starting a pipeline execution with source revision overrides

AWS CodePipeline announces the ability to start a pipeline execution with source revision overrides. Until today, a manually started pipeline execution would automatically select the “latest revision” for each source in the pipeline. The “latest revision” depended on the source action type. For example, for a CodeCommit source, the HEAD commit reference in the configured repository and branch was used, and for Amazon Elastic Container Registry (ECR) source, the latest digest of the configured image repository and tag was used. Now, when you start a pipeline execution, you can override the source revisions for the source actions in your pipeline. With this launch, you can manually start a pipeline execution and select previously successfully processed source revisions to roll back your production environment to a last known good state when the newly processed source revisions causes failures. Starting a pipeline execution with source revision override is available only with the new V2 pipeline type. To learn more about the new pipeline type, included features, and billing implications, visit the [documentation](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipeline-types.html). AWS CodePipeline is a fully managed [continuous delivery](https://aws.amazon.com/devops/continuous-delivery/) service that helps you automate your release pipelines for fast and reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of your release process every time there is a code change, based on the release model you define. To start a pipeline execution with previously processed source revisions with AWS CodePipeline, visit our [documentation](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-trigger-source-overrides.html). For more information about AWS CodePipeline, visit our [product page](https://aws.amazon.com/codepipeline/).