AWS CodePipeline supports triggering on git tags
Today, AWS CodePipeline announces support for staring a pipeline execution on git tags pushed to repositories in GitHub, GitHub Enterprise Server, GitLab Cloud and Bitbucket Cloud using CodeStarSourceConnection source actions. Customers can now add a “triggers” section in their pipeline definition that has a filter for git tags using include and exclude patterns. When a git tag applied to a commit in the source repository matches the trigger filter, CodePipeline starts a pipeline execution. The CodeStarSourceConnection action clones the commit associated with the git tag. Customers can see the git tag that started the pipeline execution in the console as output variable of the corresponding source action. Customers can use the triggers section using API/CLI/SDK and CDK. Starting a pipeline execution on git tags is available only with new V2 pipeline type. Pipelines of V2 type offer expanded features and configuration options beyond V1 type pipelines. 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 configure a pipeline to trigger on a git tag being pushed, visit our [documentation](https://docs.aws.amazon.com/codepipeline/latest/userguide/concepts.html#concepts-triggers). For more information about AWS CodePipeline, visit our [product page](https://aws.amazon.com/codepipeline/).