We performed a comparison between AWS CodeDeploy and GitLab based on real PeerSpot user reviews.
Find out in this report how the two Release Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The product is easy to use."
"It's just like every other AWS resource I use. It gets the job done."
"You can easily integrate AWS CodeDeploy with multiple services."
"AWS CodeDeploy operates on an on-demand basis. This means that you only pay for the exact duration of the deployment process. Whether it takes one minute, two minutes, or even longer, you're only charged for the time it takes to complete the deployment. You're not locked into paying for dedicated servers."
"It is very flexible."
"I found the default settings of AWS CodeDeploy to be highly beneficial for my deployment workflows. For instance, when deploying a Node.js application, I manually installed the necessary components on my AWS instance, such as the web server required by developers. Then, I created deployment scripts for starting and stopping instances and performing the deployment itself. These scripts were stored alongside my code in GitHub, ensuring they executed seamlessly with the CI/CD pipeline. Since the project wasn't overly complex, I opted for the default settings, which proved to be efficient and straightforward for deployment."
"The product's initial setup phase is easy."
"The code merging capability is something that we use very frequently."
"Key features allow creation of well-presented Wiki that includes ideas, development, and domains."
"The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good."
"The most valuable feature of GitLab is its convenience. I am able to trace back most of my changes up to a far distance in time and it helps me to analyze and see the older version of the code."
"GitLab integrates well with other platforms."
"A user friendly solution."
"We like that we can have an all-encompassing product and don't have to implement different solutions."
"The scalability is good."
"AWS CodeDeploy doesn't provide multiple plugins like Jenkins, which is a shortcoming where improvements are required."
"Deployment and stability should be improved."
"Improvements could be made to AWS CodeDeploy in terms of its agent's compatibility across different operating systems. Currently, there are instances where the agent may not work seamlessly with certain integrations, leading to issues with registering protocols on authorized servers."
"AWS should provide its own templates in the console so that I don't need to go anywhere else to get the template for AWS CodeDeploy or AWS CodeBuild."
"We have faced some issues and bugs along the way when it comes to stability."
"I faced some stability issues."
"The solution should be more cloud-native and have more cloud-native capabilities and features."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"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."
"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."
"It is a little complex to set up the pipelines within the solution."
"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."
AWS CodeDeploy is ranked 4th in Release Automation with 7 reviews while GitLab is ranked 2nd in Release Automation with 70 reviews. AWS CodeDeploy is rated 8.4, while GitLab is rated 8.6. The top reviewer of AWS CodeDeploy writes "The default settings of AWS CodeDeploy are highly beneficial for my deployment workflows". On the other hand, the top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". AWS CodeDeploy is most compared with AWS Amplify, AWS CodeStar, Microsoft Azure DevOps and Octopus Deploy, whereas GitLab is most compared with Microsoft Azure DevOps, Bamboo, SonarQube, AWS CodePipeline and Tekton. See our AWS CodeDeploy vs. GitLab report.
See our list of best Release Automation vendors.
We monitor all Release 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.
