We compared GitLab and AWS CodePipeline based on our user's reviews in several parameters.
In summary, GitLab is praised for its pricing, version control capabilities, customer service, and project management features, while users suggest improvements in UI, speed, and code review. On the other hand, AWS CodePipeline stands out for its integration with AWS services, ease of use, and automation capabilities. Users appreciate its flexible pricing and excellent customer service but seek enhancements in flexibility, UI, integration, documentation, performance, error handling, and potentially pricing.
Features: In terms of valuable features, GitLab stands out with its robust version control capabilities, seamless collaboration tools, comprehensive issue tracking system, and strong integration with other development tools. On the other hand, AWS CodePipeline is highly appreciated for its seamless integration with other AWS services, ease of use and flexibility in setting up workflows, and excellent scalability and stability.
Pricing and ROI: GitLab's setup cost is reported to be easy and straightforward, offering flexible and convenient licensing options for individuals and businesses. On the other hand, AWS CodePipeline offers simplicity and ease of setup, with fair and transparent licensing terms that suit businesses of different sizes and budgets., GitLab users have reported positive ROI and satisfaction, emphasizing the platform's value and benefits. AWS CodePipeline users have highlighted its integration, automation, and error reduction capabilities, improving workflow efficiency and software quality.
Room for Improvement: GitLab's room for improvement lies in its user interface, navigation, performance, project management features, and code review process. AWS CodePipeline, on the other hand, can enhance its flexibility, user interface, integration capabilities, documentation, performance, error handling, and pricing models.
Deployment and customer support: The user feedback for GitLab indicates a range of timeframes for deployment and setup phases, with some users considering them separate and others considering them the same period. On the other hand, user experiences with AWS CodePipeline vary greatly, with some users requiring three months for deployment and others only a week. Setup times also vary., The customer service of both GitLab and AWS CodePipeline products has been highly praised by users. Users appreciate the prompt assistance and knowledgeable support team of both products. However, GitLab is known for consistently going above and beyond to resolve issues and address concerns, while AWS CodePipeline has been commended for its responsiveness and availability of customer service.
The summary above is based on 57 interviews we conducted recently with GitLab and AWS CodePipeline users. To access the review's full transcripts, download our report.
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"The product is cost-effective and integrates well with the AWS environment."
"The integrations are good."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"AWS CodePipeline has valuable integration features."
"The product is a one-stop solution that you can use to integrate, deploy and host your application."
"Code deployment is the best feature."
"This is a scalable solution. We had around 200 users working with it."
"A user friendly solution."
"It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience."
"It's a great toolbox where the CI/CD pipeline is the fundamental component, but there are so many other features that you can pull from, which makes it a very powerful tool. My current client is using AWS, and they can, of course, use AWS CodePipeline, but GitLab is much more mature than that, and it also gives you the freedom to decide to go to another platform or have a multi-cloud strategy and things like that. That freedom for me is also very valuable."
"We're only using the basic features of GitLab and haven't used any advanced features. The solution works fine, so that's what we like about GitLab. We're party using GitHub and GitLab. We have a GitHub server, while we use GitLab locally or only within our team, and it works okay. We don't have any significant problems with the solution. We also found the straightforward setup, stability, and scalability of GitLab valuable."
"It scales well."
"I have found the most valuable feature is security control. I also like the branching and cloning software."
"We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people."
"It would be a much better tool if it could be made compatible with other cloud services as well since this is an area the product currently lacks."
"The migration process from one source code to another needs improvement."
"The product’s pricing needs improvement."
"The solution could improve the documentation. Sometimes we have some issues with the documentation not updating after releasing .NET 6. We had some issues with building the code pipeline, and it was not updating the documentation. It's better to update the code documentation."
"If there are many dependancies involved in the setup, it may take a long time."
"The tool does not provide automated features for evidence collection."
"AWS CodePipeline functions well, but there's room for improvement in providing technical support to regular customers who haven't purchased developer support. I mean, having it available for everyone, even if it's not a 24-hour service. It would be more useful if specific support hours were available for assistance."
"In the next release, I would like to see fewer timeout errors."
"We'd like to see better integration with the Atlassian ecosystem."
"When deploying the solution on cloud and the CI/CD pipeline, we have to define the steps and it becomes confusing."
"For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better."
"We'd always like to see better pricing on the product."
"I used Spring Cloud config and to connect that to GitLab was so hard."
"GitLab's Windows version is yet not available and having this would be an improvement."
"The solution should be more cloud-native and have more cloud-native capabilities and features."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
AWS CodePipeline is ranked 3rd in Build Automation with 13 reviews while GitLab is ranked 1st in Build Automation with 70 reviews. AWS CodePipeline is rated 8.4, while GitLab is rated 8.6. The top reviewer of AWS CodePipeline writes "A fully managed service with excellent integrations and a flexible architecture". On the other hand, the top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". AWS CodePipeline is most compared with AWS CodeStar, Jenkins, GitHub Actions, Tekton and Bamboo, whereas GitLab is most compared with Microsoft Azure DevOps, Bamboo, SonarQube, Tekton and TeamCity. See our AWS CodePipeline vs. GitLab report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.