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 integrations are good."
"The tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier."
"It's a perfect solution if you are just using AWS."
"The integration with other applications is fabulous."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"Code deployment is the best feature."
"I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand."
"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
"This is a scalable solution. We had around 200 users working with it."
"The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline."
"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."
"The dashboard and interface make it easy to use."
"The code merging capability is something that we use very frequently."
"For us, Gitlab's most valuable feature is the integration with Cypress. We're using Cypress as an automation tool, so we're using GitLab as a tool for running in parallel."
"There could be a possibility of deploying tag-based conditions for different environments using the same code base."
"The tool does not provide automated features for evidence collection."
"The product’s pricing needs improvement."
"In the next release, I would like to see fewer timeout errors."
"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."
"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."
"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."
"If you're talking about multi-cloud, you can't use it."
"The price of GitLab could improve, it is high."
"GitLab can improve the integration with third-party applications. It could be made easier. Additionally, having API control from my application could be helpful."
"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."
"I would like to have some features to support peer review."
"The initial setup was quite challenging because it takes some time to understand how to pull out or push the code."
"We'd always like to see better pricing on the product."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"The solution does not have many built-in functions or variables so scripting is required."
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.