GitLab vs Inedo BuildMaster comparison

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

"I have found the most valuable features of GitLab are the GitClone, GitPush, GitPull, GitMatch, GitMit, GitCommit, and GitStatus."

"Git hosting has an integration with ACD which is why we liked this solution in the first place."

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

"GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team."

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

"We use GitLab in the new project for CI/CD, integration, and deployment."

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

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

"I'm new to GitLab, so I would appreciate more documentation about the code and commands."

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

"It is a little complex to set up the pipelines within the solution."

"We do face issues in our company when we run out of disk space."

"It would be really good if they integrated more features in application security."

"GitLab should work on improving their user interface for GitOps as it is lagging behind."

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

"The licensing model could be improved to be more accommodating in terms of user numbers and costs."

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

"GitLab is cheap."

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

"It is very expensive. We can't bear it now, and we have to find another solution. We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year."

"My company uses the free version of GitLab, which is GitLab Community Edition. There is a licensed version also available for GitLab."

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

"The solution is based on a subscription model and is reasonably priced."

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

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