We performed a comparison between GitLab and UrbanCode Deploy 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 most valuable features of GitLab are ease of use and highly intuitive UI and performance."
"I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand."
"It is very flexible and easy because you can store data on cloud."
"It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience."
"We have seen a couple of merge requests or pull requests raised in GitLab. I see the interface, the way it shows the difference between the two source codes, that it is easy for anyone to do the review and then accept the request; the pull request is the valuable feature."
"The SaaS setup is impressive, and it has DAST solutioning."
"It's a great toolbox where the CI/CD pipeline is the fundamental component, but there are so many other features that you can pull from, which makes it a very powerful tool. My current client is using AWS, and they can, of course, use AWS CodePipeline, but GitLab is much more mature than that, and it also gives you the freedom to decide to go to another platform or have a multi-cloud strategy and things like that. That freedom for me is also very valuable."
"The code merging capability is something that we use very frequently."
"It is very easy to make a software release. It used to take us at least a couple of hours to make a release, now we went to production with a new one last night. This new release took me five minutes."
"Stable solution that's good for automating the CI/CD pipeline: from development to production."
"The most valuable functionality is the ability to define the deployment process, schedule the deployment and automatically execute the deployments to different environments."
"The most valuable feature is the snapshot functionality, which allows us to access previous versions of the artifacts."
"The stability is good. I haven't experienced any issues."
"The solution handles complex deployments very efficiently."
"GitLab could consider introducing a code-scanning tool. Purchasing such tools from external markets can incur charges, which might not be favorable. Integrating these features into GitLab would streamline the pipeline and make it more convenient for users."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"The solution should be more cloud-native and have more cloud-native capabilities and features."
"It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain. If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain."
"Their RBAC is role-based access, which is fine but not very good."
"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."
"This solution could be improved by adding modifications such as slack notifications."
"When deploying the solution on cloud and the CI/CD pipeline, we have to define the steps and it becomes confusing."
"The technical support of the solution could definitely be improved as PMRs take long to resolve."
"I certainly would like to have a better way to pass information between deployment steps using UrbanCode Deploy because that's really difficult to do."
"I would like to have the agent up and running at all times, as opposed to only while it is in the DevOps pipeline."
"The scalability of this application needs improvement. Changes and variations in the application become bottlenecks as they need to be more seamless and comfortable."
"The interface allows access in a number of ways but that can be confusing."
"I would like to see more reporting for container architecture."
GitLab is ranked 2nd in Release Automation with 70 reviews while UrbanCode Deploy is ranked 6th in Release Automation with 27 reviews. GitLab is rated 8.6, while UrbanCode Deploy is rated 7.8. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of UrbanCode Deploy writes "It offers OOTB plugins for middleware". GitLab is most compared with Microsoft Azure DevOps, SonarQube, Bamboo, AWS CodePipeline and SonarCloud, whereas UrbanCode Deploy is most compared with Red Hat Ansible Automation Platform, Microsoft Azure DevOps, Octopus Deploy, HCL Launch and BMC Release Lifecycle Management. See our GitLab vs. UrbanCode Deploy 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.
