CodePipeline supports GitLab self-managed
You can now use projects from your GitLab self-managed instance (GitLab Enterprise Edition, GitLab Community Edition) to build, test, and deploy code changes using AWS CodePipeline. You can connect your GitLab self-managed instance that is in a VPC or directly accessible using AWS CodeStar Connections, and use the connection in your pipeline to automatically start a pipeline execution on changes in your repository.
You can now use projects from your GitLab self-managed instance (GitLab Enterprise Edition, GitLab Community Edition) to build, test, and deploy code changes using AWS CodePipeline. You can connect your GitLab self-managed instance that is in a VPC or directly accessible using AWS CodeStar Connections, and use the connection in your pipeline to automatically start a pipeline execution on changes in your repository.
AWS CodePipeline is a fully managed 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. This launch extends AWS CodePipeline’s existing source control provider support, including AWS CodeCommit, Bitbucket Cloud, GitHub.com, GitHub Enterprise Server, and GitLab.com.
To learn more about using GitLab self-managed with AWS CodePipeline, visit our documentation. For more information about AWS CodePipeline, visit our product page. The new feature is available in all regions where AWS CodePipeline is supported except in the Asia Pacific (Hong Kong), Africa (Cape Town), Middle East (Bahrain), Europe (Zurich), Asia Pacific (Jakarta), Asia Pacific (Hyderabad), Asia Pacific (Osaka), Asia Pacific (Melbourne), Israel (Tel Aviv), Europe (Spain), and Middle East (UAE), and the AWS GovCloud (US-West) Regions.