We performed a comparison between GitLab and Harness based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation."GitLab integrates well with other platforms."
"It speeds up our development, it's faster, safer, and more convenient."
"The most valuable feature of GitLab is the ability to upload scripts and make changes when needed and then reupload them. Additionally, the solution is user-friendly."
"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
"It scales well."
"The stability is good."
"The user interface is really good so that helps with huge teams who need to collaborate."
"We're only using the basic features of GitLab and haven't used any advanced features. The solution works fine, so that's what we like about GitLab. We're party using GitHub and GitLab. We have a GitHub server, while we use GitLab locally or only within our team, and it works okay. We don't have any significant problems with the solution. We also found the straightforward setup, stability, and scalability of GitLab valuable."
"It's a highly customizable DevOps tool."
"It would be really good if they integrated more features in application security."
"The pricing model of GitLab is an issue for me."
"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."
"I used Spring Cloud config and to connect that to GitLab was so hard."
"I would like to see better integration with project management tools such as Jira."
"GitLab could add a plugin to integrate with Kubernetes stuff."
"GitLab doesn't have AWS integration. It would be better to have integration with other container management environments beyond Kubernetes. It has very good integration with Kubernetes, but it doesn't have good integration with, for example, AWS, ETS, etc."
"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."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
GitLab is ranked 1st in Build Automation with 70 reviews while Harness is ranked 8th in Build Automation with 1 review. GitLab is rated 8.6, while Harness is rated 7.0. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of Harness writes "Provides a good graphical interface, but the initial setup process needs improvement ". GitLab is most compared with Microsoft Azure DevOps, SonarQube, Bamboo, AWS CodePipeline and Tekton, whereas Harness is most compared with Tekton, Jenkins, Bamboo, GitHub Actions and AWS CodePipeline.
See our list of best Build Automation vendors and best Static Application Security Testing (SAST) 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.
