AWS CodeBuild vs GitLab comparison

"The integration with other AWS services has streamlined our workflow."

"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."

"The solution provides good integrations."

"It works seamlessly with AWS Elastic Container Registry (ECR)."

"The integration is a good feature."

"The initial setup of CodeBuild is easy."

"The integration is a good feature."

"One of the main features I value in CodeBuild compared to previous experiences, like using Jenkins, is its ability to handle tasks automatically with AWS, requiring only proper setup of the check file."

"CI/CD and GitLab scanning are the most valuable features."

"Of all available products, it was the easiest to use and easy to install."

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

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

"The dashboard and interface make it easy to use."

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

"We use the Git repository and tagging feature. We are a product-based company and use this solution to move to a forward or backward tag."

"The code merging capability is something that we use very frequently."

"There is no persistent storage or preservation of workspace between the builds."

"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."

"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."

"Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds."

"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."

"They can further improve the integration of the Bitbucket for CodeBuild."

"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."

"The deployment fails sometimes."

"The only thing our company is really waiting on in terms of features is the development of metrics."

"It should be used by a larger number of people. They should raise awareness."

"The pricing has been substantially increased, which is a major concern."

"The documentation could be improved to help newcomers better understand things like creating new branches."

"Their RBAC is role-based access, which is fine but not very good."

"As GitLab is not perfect, what needs improvement in the solution is the Wiki feature of the groups or the repertories because currently, it's not searchable by default. You'll need an indexing service such as Elasticsearch to make it searchable, and that requires too much work, so for me, it's the main feature that should be improved in GitLab. In the next version of the solution, from the top of my head, the documentation could be improved. Besides the Wiki, it would be good if there's documentation that would be automatically generated based on the code repository. In other words, there should be some tutorials from GitLab for developers in the next release."

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

"We do face issues in our company when we run out of disk space."

"Despite the cost, it is worth the investment."

"We pay a monthly licensing fee."

"AWS CodeBuild is free. We only pay for our code's compute resources during the build process. For example, if our code takes ten minutes to build, we only pay for those ten minutes of computing time. CodeDeploy and CodePipeline are free because they're serverless and don't require computing resources. CodeCommit has minimal costs for storing code."

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

"In terms of the pricing for GitLab, on a scale of one to five, with one being expensive and five being cheap, I'm rating pricing for the solution a four. It could still be cheaper because right now, my company has a small team, and sometimes it's difficult to use a paid product for a small team. You'd hope the team will grow and scale, but currently, you're paying a high license fee for a small team. I'm referring to the GitLab license that has premium features and will give you all features. This can be a problem for management to approve the high price of the license for a team this small."

"This product is not very expensive but the price can be better."

"The price is okay."

"The open-source version is very good and the commercial version is reasonably priced."

"We are using the free version of GitLab."

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

"The solution's pricing is acceptable."