AWS CodeDeploy vs GitLab comparison

"It's just like every other AWS resource I use. It gets the job done."

"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."

"You can easily integrate AWS CodeDeploy with multiple services."

"It is very flexible."

"I can integrate it with other AWS services."

"The product is easy to use."

"The product's initial setup phase is easy."

"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 scalable."

"GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team."

"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."

"The most valuable feature of GitLab is the automatic merging of code."

"In our software development lifecycle, GitLab is used as a component for code repository management. We use GitLab for several projects to handle code repositories. For other software projects, we use Bitbucket, but the use case for both is very similar."

"The most valuable features of GitLab are the review, patch repo, and plans are in YAML."

"The SaaS setup is impressive, and it has DAST solutioning."

"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 CodeDeploy doesn't provide multiple plugins like Jenkins, which is a shortcoming where improvements are required."

"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."

"The support and those things are lacking compared to others."

"I faced some stability issues."

"I would like to see better integration with project management tools such as Jira."

"The solution does not have many built-in functions or variables so scripting is required."

"The tool should include a feature that helps to edit the code directly."

"Expand features to match other tools such as a static code analysis tool so third-party integrations are not required."

"It would be really good if they integrated more features in application security."

"I'm new to GitLab, so I would appreciate more documentation about the code and commands."

"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."

"Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."

"The product's price is normal."

"It is costly."

"Since we are using a dedicated AWS environment, the solution's pricing is fine."

"AWS CodeDeploy has proven to be a cost-effective solution for us, especially considering the benefits we gain from using it. In terms of pricing, AWS is quite affordable, providing excellent value for the features and services it offers."

"The product is free with EC2."

"Regarding pricing, I would rate GitLab as moderately priced, maybe around a seven or eight out of ten. It could be more flexible for clients but generally offers good value."

"The price of GitLab could be better, it is expensive."

"Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."

"I'm not sure if they have some kind of discount. I've been negotiating with them on prices before, and I believe they weren't too happy to give discounts, but list prices are $19 per user, per month for Premium and $99 per user, per month for Ultimate. So, the difference between Premium and Ultimate is a bit bigger, and in most companies, you need to build some type of business case."

"We are using the open-source version."

"We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive."

"The solution is based on a licensing model that includes technical support and is paid annually."

"There are different licensing options available, including a free limited-user license."