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.
"AWS CodePipeline has valuable integration features."
"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"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 product is a one-stop solution that you can use to integrate, deploy and host your application."
"The integration with other applications is fabulous."
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"The product is cost-effective and integrates well with the AWS environment."
"This product is always evolving, and they listen to the customers."
"GitLab's best features are continuous integration and fast deployment."
"The most important features of GitLab for us are issue management and all the CI/CD tools. Another aspect that I love about GitLab is the UI."
"The stability is good."
"CI/CD is very good. The version control system is also good. These are the two features that we use."
"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
"The most valuable features of GitLab are the CI/CD pipeline and code management."
"A user friendly solution."
"The migration process from one source code to another needs improvement."
"The setup time is a bit long."
"The tool does not provide automated features for evidence collection."
"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."
"AWS CodePipeline doesn't offer much room for customization."
"In the next release, I would like to see fewer timeout errors."
"There could be a possibility of deploying tag-based conditions for different environments using the same code base."
"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's more related to the supporting layer of features, such as issue management and issue tracking. We tend to always use, for example, Jira next to it. That doesn't mean that GitLab should build something similar to Jira because that will always have its place, but they could grow a bit in those kinds of supporting features. I see some, for example, covering ITSM on a DevOps team level, and that's one of the things that I and my current client would find really helpful. It's understandably not going to be their main focus and their core, and whenever you are with a company that needs a bit more advanced features on that specific topic, you're probably still going to integrate with another tool like Jira Service Management, for example. However, some basic features on things like that could be really helpful."
"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."
"The price of GitLab could improve, it is high."
"Some of the scripts that we encountered in GitLab were not fully functional and threw up errors."
"The pricing model of GitLab is an issue for me."
"Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."
"I rate the support from GitLab a four out of five."
"Based on what I know so far, its integration with Kubernetes is not so good. We have to develop many things to make it work. We have to acquire third-party components to work with Kubernetes."
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.
