GitLab vs Harness comparison

"The user interface is really good so that helps with huge teams who need to collaborate."

"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."

"GitLab's best features are maintenance, branch integration, and development infrastructure."

"GitLab's best feature is Actions."

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

"GitLab is very well-organized and easy to use. Also, it offers most features that customers need."

"When a developer checks in code, it is automatically built and deployed, and automated test cases are also run. We have extensive integration with GitLab, which helps us with source code management. We run the static code analysis using SonarQube."

"I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently."

"It's a highly customizable DevOps tool."

"Harness starts integrating with organizations, making everything automated without the need for manual interruption."

"GitLab can improve by integrating with more tools, such as servers with Docker."

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

"Even if I say I want some improvement, they will say it is already planned in the first quarter, second quarter, or third quarter. That said, most everything is quite improved already, and they're improving even further still."

"It's more related to the supporting layer of features, such as issue management and issue tracking. We tend to always use, for example, Jira next to it. That doesn't mean that GitLab should build something similar to Jira because that will always have its place, but they could grow a bit in those kinds of supporting features. I see some, for example, covering ITSM on a DevOps team level, and that's one of the things that I and my current client would find really helpful. It's understandably not going to be their main focus and their core, and whenever you are with a company that needs a bit more advanced features on that specific topic, you're probably still going to integrate with another tool like Jira Service Management, for example. However, some basic features on things like that could be really helpful."

"Some of the scripts that we encountered in GitLab were not fully functional and threw up errors."

"GitLab's UI could be improved."

"In the next release, I would like to see GitLab expand its integration capabilities to include platforms like DigitalOcean, which developers widely use for cloud infrastructure. Enhancing CI/CD automation features specifically tailored for DigitalOcean would be beneficial."

"GitLab could add a plugin to integrate with Kubernetes stuff."

"Even with automation, there's a requirement for manual change requests for approvals."

"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."

"As I work in a vast enterprise, I'm unsure about the licensing cost for GitLab. It's the management team that takes care of that."

"GitLab's pricing is good compared to others on the market."

"We are currently using the open-source version."

"I don't mind the price because I use the free version."

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

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

"GitLab is an open-source solution."