GitLab vs Inedo BuildMaster comparison

"It scales well."

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

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

"GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable."

"GitLab offers a good interface for doing code reviews between two colleagues."

"I like that it's easy to deploy our services over GitLab. The customer support is also good with a really active community. You have a lot of support that you can get online with your stack. That is probably one of the benefits of using GitLab. It's also really fast."

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

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

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

"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."

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

"Atlassian offers more products than GitLab. GitLab offers source control management, version control and collaboration between developers. Atlassian offers features on top of this as well as more integration points for developers."

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

"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."

"There is room for improvement in GitLab Agents."

"We'd always like to see better pricing on the product."

"It could have more security integrations and the ability to check the vulnerability of the code. I don't think it is a responsibility of Gitlab, but it would be nice to have more options to integrate with."

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

"This is an open-source solution."

"GitLab is an open-source solution."

"GitLab is comparatively expensive, but it provides value because it's feature-rich."

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

"GitLab is a free solution to use."

"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 sure if they have some kind of discount. I've been negotiating with them on prices before, and I believe they weren't too happy to give discounts, but list prices are $19 per user, per month for Premium and $99 per user, per month for Ultimate. So, the difference between Premium and Ultimate is a bit bigger, and in most companies, you need to build some type of business case."

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