GitLab vs Inedo BuildMaster comparison

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

"The solution's service delivery model is fantastic."

"We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people."

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

"They incorporate new features every September, and they have introduced their own code editor and AI features."

"The most valuable features of GitLab are the CI/CD pipeline and code management."

"The most valuable aspects of GitLab are the ability to create branches, merge branches, and compare branches to resolve code conflicts."

"CI/CD is valuable for me."

"Technical support is quick to respond. I haven't had any issues with them."

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

"There are some challenges with repository file management as GitLab may struggle to manage larger files."

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

"I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button."

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

"In the free version, when a merge request is raised, there is no way to enforce certain rules. We can't enforce that this merge request must be reviewed or approved by two or three people in the team before it is pushed to the master branch. That's why we are exploring using some agents."

"I used Spring Cloud config and to connect that to GitLab was so hard."

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

"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."

"The price is okay."

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

"I think that we pay approximately $100 USD per month."

"The solution's standard license is paid annually. They have changed the pricing model and it used to be better. There is a free version available."

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

"I'm not aware of the licensing costs because those were covered by the customer."

"GitLab is an open-source solution."

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