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.
"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"AWS CodePipeline has valuable integration features."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"The integration with other applications is fabulous."
"The product is cost-effective and integrates well with the AWS environment."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"Code deployment is the best feature."
"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 SaaS setup is impressive, and it has DAST solutioning."
"GitLab is kind of an image of GitHub, so it gives us the flexibility to monitor our changes in the repos."
"I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently."
"I have had no problem with the stability of the solution."
"Key features allow creation of well-presented Wiki that includes ideas, development, and domains."
"The most valuable features of GitLab are the review, patch repo, and plans are in YAML."
"CI/CD and GitLab scanning are the most valuable features."
"As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab."
"If there are many dependancies involved in the setup, it may take a long time."
"The migration process from one source code to another 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 you're talking about multi-cloud, you can't use it."
"The setup time is a bit long."
"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."
"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 solution does not have many built-in functions or variables so scripting is required."
"There is room for improvement in GitLab Agents."
"There was a problem with the build environment when we were looking at developing iOS applications. iOS build require Mac machines and there are no Mac machines provided by GitLab in their cloud. So to build for mobile iOS application, we needed to use our own Mac machine within our own infrastructure. If GitLab were to provide a feature such that an iOS application could also be built through GitLab directly, that would be great."
"It could have more security integrations and the ability to check the vulnerability of the code. I don't think it is a responsibility of Gitlab, but it would be nice to have more options to integrate with."
"The tool should include a feature that helps to edit the code directly."
"Atlassian offers more products than GitLab. GitLab offers source control management, version control and collaboration between developers. Atlassian offers features on top of this as well as more integration points for developers."
"The user interface could be more user-friendly. We do most of our operations through the website interface but it could be better."
"GitLab's UI could be improved."
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.