GitLab vs JFrog Pipeline comparison

"Key features allow creation of well-presented Wiki that includes ideas, development, and domains."

"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 have an all-encompassing product and don't have to implement different solutions."

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

"Continuous integration with deployment is very powerful, which is a significant reason for migrating from TFS to GitLab."

"GitLab is scalable and works well with multiple environments."

"Everything is easy to configure and easy to work with."

"The most valuable feature of GitLab is its convenience. I am able to trace back most of my changes up to a far distance in time and it helps me to analyze and see the older version of the code."

"The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."

"Testing against multiple run times, versions, and environments is a plus point with the additional pipelines making it more interesting to see what is happening across your development process in a single pane of glass."

"The integration could be slightly better."

"For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better."

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

"GitLab could improve the patch repository. It does not have support for Conan patch version regions. Additionally, better support for Kubernetes deployment is needed as part of the package."

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

"I would like configuration of a YML file to be done via UI rather than a code file."

"I would like to see AI support in GitLab."

"I don't really like the new Kubernetes integration because it is pretty focused on the on-premise environment, but we're in a hybrid environment."

"They could work on reducing the number of permissions required while using Bitbucket."

"We are using the open-source version."

"GitLab is an open-source solution."

"Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."

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

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

"We are using the free version of GitLab."

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

"The price of GitLab could be better, it is expensive."

"The pricing is the cheapest compared to the other platforms out there."