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.
"The product is cost-effective and integrates well with the AWS environment."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"It's a perfect solution if you are just using AWS."
"Code deployment is the best feature."
"AWS CodePipeline has valuable integration features."
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"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."
"The integration with other applications is fabulous."
"The most valuable features of GitLab are the review, patch repo, and plans are in YAML."
"GitLab offers a good interface for doing code reviews between two colleagues."
"The solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people."
"Everything is easy to configure and easy to work with."
"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."
"I have found the most valuable features of GitLab are the GitClone, GitPush, GitPull, GitMatch, GitMit, GitCommit, and GitStatus."
"GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team."
"Git hosting has an integration with ACD which is why we liked this solution in the first place."
"AWS CodePipeline doesn't offer much room for customization."
"The migration process from one source code to another needs improvement."
"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."
"If there are many dependancies involved in the setup, it may take a long time."
"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."
"In the next release, I would like to see fewer timeout errors."
"GitLab could add a plugin to integrate with Kubernetes stuff."
"GitLab can improve the integration with third-party applications. It could be made easier. Additionally, having API control from my application could be helpful."
"I would like to see better integration with project management tools such as Jira."
"There is room for improvement in GitLab Agents."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"Even if I say I want some improvement, they will say it is already planned in the first quarter, second quarter, or third quarter. That said, most everything is quite improved already, and they're improving even further still."
"I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button."
"I don't really like the new Kubernetes integration because it is pretty focused on the on-premise environment, but we're in a hybrid environment."
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.
