GitLab Reviews

I am not constrained at all by a company like GitHub or Bitbucket. It allows my team to have faith that what we are working on - remains in house. For piece of mind - without using git native.

Difficult to setup for the uninitiated linux administrator. Administration and upgrades are also difficult to do.

GitLab is a superb source code managemanet provide. It is free. We can install it in our privet server also. As well as we can use their server with a free account. We use git for version control. GitLab provides awesome support for version control. It is a very easy tool. Anyone can use it very easily If someone has no more knowledge about versioning but He can use GitLab very easy. We can maintain our Repositories/Branchers. User access level also there. Currently, We use GitLab. We maintain feature branches, dev branch, and master branch. Everyone does not allow to merge code to the dev branch. If someone add merge request to the dev branch, our one-person review code and merge. Then we use GitLab it is easy for us. GitLab provides superb dashboard it very easy to review code. It shows all code changes with file by file. Easy to compare. As well as we can compare two branches vary easy. It provides a clear, unique, user-friendly dashboard. GitLab also supports CI/CD process. It's superb we can recommend for anyone. If our commit has some conflict it shows how to resolve that step by step.

When I add a new commit. If the file is large/have many lines. It not showing code changes directly. It shows a message file has many lines cannot show changes that kind of message. Sometimes when we compare two commits. It not more clear. Some times confusing. If I show some file history only show commits. not showing code changes by commits. We want to go and check every commits to show changes.

In software development lifecycle gitlab has very integrated approach and it has built in CI/CD pipelines.And It is very user friendly even though it is for developers.

It's documentation is not that much easy to understand and even though it has so many features, new user might find himself/herself lost in getting to be aware.

The products has plenty of features, as well as supporting all the basic Git operations/merge requests, you are given a wide choice of CI pipelines you can set up from within the project. Need more? Integrations with metrics, error tracking, kubernetes, snippets and more.
I never had any problem so far, it's stable and always up.

The major issue for me is that these features are advanced, and if you want to use the repository as just that, you find yourself overwhelmed with loads of choices that you don't really need. Therefore, sometimes I find it hard to look for a button which should be the most visible element on the screen. Additionally, I found the arrangement of information in the "merge request" screen a bit counterintuitive compared with similar services.

You just forget about Gitlab. As it provide a whole devops toolkit, it integrates discretely in your workflow. It doesn't require training, and if needed for advanced use, it got an extensive documentation as any open source tool should have. The UI makes it easy to use without thinking about it. What you don't understand first, you'll find an usage if needed on day.

The fact it got integrated CI/CD is incredible. I am very reluctant to Docker technologies and wouldn't beat myself to deal with them, but I really like them the way they are integrated in the CI/CD: it makes possible to test the applications in a very efficient and simple maneer and improve the overall quality and security of my products.

What I really don't like is that, if it is possible do deactivate some feature of a repository because you don't use them, there are some that overload the UI and you cannot remove them because Gitlab use it as a way to make you upgrade to the next plan.

It's opensource though provides a cloud based solution with a really good free tier. It allows integrating code repositories with issue tracking and continuos integration and continuos deployment

User experience could be largely improved. Searching and filters are a bit clunky from the UX point of view. Also bulk actions are only allowed at project level.

GitLab provides all-in-one capability for developers to do Source Code Management, CI/CD automation, Security and coding standards checks. Earlier we used to have separate tools for each of the above functions, but moving to Gitlab we now have a single stop-shop for all our Application Development and Automation needs. I see many other companies are trying to follow the gitlab methodology but gitlab is way ahead of the competetion.

Project and Portfolio management can still have improvements to provide Roadmap and Grantt views in future versions

GitLab CI is great. The GitLab CI/CD language allows us to build complex pipelines easily, pipeline's configs are stored in the repository as well, so we can manage everything in one place. GitLab also has built-in Docker registry. We have both our build pipeline and our images hosted on GitLab.
The pricing is also flexible, I recommend it for both startup and large enterprises.

Explore Projects feature can be better, it would be more useful if we have a filter to select projects by technologies.
Should support templates on the job level, so it can be reused between multiple environments.
Lack of integration: there are not many 3rd party services that integrate with GitLab for now.

The most important feature is source code managing tool. App provides interface for GIT client. Creating a merge request is easy and you don't need to use console, it is possible to achieve this goal also on mobile! Another most important feature is CI/CD integration. Gitlab provides its solution to do this. You can define configuration and run tasks on GitLab runner, which can be easily installed on any server.

It provides a less functions than other software and a UI is a bit non modern.

GitLab does its best to help you with what you may need in order to promote quality code deployments with tools and resources to become a more collaborative team. With source control and hosting repositories as its primary objective, GitLab extends to its users an extensive suite of tools and controls to ensure only quality code is committed and only by those that is desired. With features like code reviews, pipeline validations, and allowing for integration of automated tests, its hard to imagine low quality or bug infested code to get through to your production or master code branches.

Honestly, its not easy to pick out cons of such a great tool in your arsenal. Given that so much goes so well once you've integrated everything properly, the only things that come to mind are more of a annoyance rather than an issue and coincidentally, they're all based on the UI or aspects that don't interfere with the workflow or the work itself. One of which is that GitLab does not offer a dark mode of its UI. Given we are developers and spend most of our time looking at computer screen, It would be lovely to be able to darken the UI so that its not so straining to our eyes. Secondly, we have split up our GitLab in to various teams where each of the teams have access to their own folders/repository. Unfortunately, whenever someone from ANY of these sub-repos is given access, opens a new merge request, or is making comments on a merge request, everyone gets an email about it. It can be very frustrating and I'm not really sure if this setting can be changed from a User level but I would really love it if they can.

One of the things I admire most about GitLab is its open-source nature, which means that a vast community of users is constantly working to expand the platform's capabilities and use cases. I am particularly impressed with GitLab's robust branching and merging capabilities, which enhance its version control protocol and make it easy to manage even the most complex codebases by providing access to all versions of our codebase.

When working with large codebases on GitLab with multiple collaborators, it's not uncommon to experience slower load times and sluggish navigation. Additionally, while GitLab offers a range of integrations with third-party tools and services, there is certainly room for improvement in this area.

I've tried them all from Github to Bitbucket. I think that Gitlab is an optimal tool since it not only provides repository management but also a lot of useful tools to make your DevOps process much easier. I find it perfect when it comes to code review thanks to the comments and approval system.

Sometimes it is not so easy to find what you are looking for and you have to dig in the settings