GitLab Reviews

GitLab's most impactful features are its integrated CI/CD pipeline, version control, and collaboration tools. The product has a bit of a learning curve but is generally considered easy to use. GitLab's integration with existing business processes was easy as there are many options for customization and automation. Onboarding is very easy for most developers which is why our organization has chosen it over other tools.

We have expected better performance overall but it was sluggish at times. so that can be improved.Intuitive user interface is also very important where gitlab lags a littleRobust project management capabilities can be brought in. If there is more comprehensive documentation then it will really help lot of people in the industry

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.

I have started using this when I was an undergraduate and I'm still using this in my IT company too. I can create repositories, projects, branches and can manage the source code there. I can review someone elses' code and add comments and merge it once the code fixes are done. It allows to automate the pipeline with the help of integrating other tools.

I haven't face any issue using gitlab so far.

The software is stable.
Updates come out regularly.
SSO integration with our AD is very nice.

We are using gitlab not only for our source code, but also to control the configuration of all of our servers and firewalls. It would be nice if we could schedule scripts on gitlab to run automatically. We are now 'abusing' the pipelines for this purpose.

Makes it easy to search for commits and also manage the evolution of the code base as the code progresses. It also makes it easier to search for files and also switch between branches to view the files at different branches.

Nothing much to complain about. I would say maybe make it easier to configure build variables but even that is not too difficult

GitLab is a very easy to use software that helps our project and the project management department. It helps in managing work.

The features are good however we experience certain slowness regardless of that I can recommend GitLab to others for the IT management.

GitLab offers a complete DevOps platform, greatly increasing productivity and cooperation. Its user-friendly design and robust capabilities make it possible to organise source code effectively, streamline processes, and collaborate with ease. To ensure high-quality deliveries, teams may manage code with ease, keep track of changes, and perform code reviews. The automated CI/CD pipelines free up time for innovation by automating monotonous processes. Teams can share knowledge, manage issues, and debate code using the built-in collaboration features, which promote collaboration. GitLab's emphasis on productivity and teamwork ultimately results in shorter development cycles, more effectiveness, and improved teamwork.

Complexity of Configuration and Setup and Due to GitLab's wide variety of features and settings, the initial setup and configuration procedure might be challenging.

I use this to create branches, projects and repositories, merge the code, review the code and add comments after reviewing and document the code. It is a very powerful tool and we can automate the process of code build, testing an deployment.

So far, I haven't faced any issue using this.

Security is better when comparing with others.Git repository hosting and version control is available.

Bit expensive than other services in the market.

One of most advanced source code manager in the market. Adding or creating private keys for the projects are very easy.

Very expensive for startups or smaller teams.

This product is excellent and has both enterprise edition and community edition making it very inexpensive to get into and then moving to enterprise once setup and still very inexpensive compared to other options out there. You also can set up a private gitlab server either in docker or bare metal. I cannot rave enough about git lab.

There's not much to not like about it. It's a very capable system that can be deployed in every type of way imaginable. If I was to nitpick then I would say adding additional users can be a pain without having self registration available.

GitLab is easy to use and offers a versatile range of applications. GitLab can be used not only for software development projects. Especially in the academic sector, institutions can use GitLab to persist the respective work steps and research data, data in general, and workflows. Version control is particularly helpful in this regard, as it allows each step of a work to be traced, and errors to be undone directly without having to do a great deal of extra work.
In addition, GitLab can be customized and the respective instances can be easily transferred to one's own infrastructure. The development team is also always open to new ideas and actually incorporates them.

GitLab is therefore not only suitable for software development, but for any form of project in which it is a matter of the step-by-step tracking of work steps.

GitLab can be quite overwhelming. It is particularly difficult for non-experts from the non-software sector to get to know the processes of GitLab, as GitLab is less focused on gamification aspects compared to GitHub. Therefore, a high level of preparatory work and expertise is required in GitLab. Likewise, GitLab is often very technical, which is understandable, but it would be quite conceivable that especially in the area of testing and CI, modular principles, like for websites, would be conceivable and desirable.

Integration of CI/CD and Kubernetes for easily developing and running custom apps. Fantastic collaboration features like discussions, visual diffing. Some of this stuff you don't even get on desktop apps that charge big bucks. Frequent updates that inch its capability and usability forward. Good documentation. Wonderful community, welcoming atmosphere, pleasant to work with all the employees I've encountered.

Sometimes things break. When things are broken, sometimes it can take some time to be fixed, if you're not willing or able to fix it yourself. One of the consequences of such broad scope and feature development velocity. It would be advisable to keep another copy installed separately for testing updates before applying them to the live edition, if your IT has the capacity to do so.

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.

GitLab is an incredibly powerful and efficient code management tool. It is incredibly user-friendly and allows for easy code collaboration between developers. Its user interface is easy to navigate and understand. Additionally, it has a wide variety of features such as code review and project management that make it a great choice for any development team.

The only downside to GitLab is that it can be a bit overwhelming for new users. It has a lot of features, which can make it difficult to understand. Additionally, the pricing can be a bit high for smaller teams or individual developers.

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

For us, it was crucial to be able to self host an instance to have it totally off grid and Gitlab delivered beautifully

A bit obscure to setup, and updates can be quite time consuming as we cannot do them as often as would be required by the project

GitLab comes packed with a number of helpful facilities for managing continuous integration/deployment tasks. The option to self-host a GitLab instance is also appreciated.

Comes with something of a learning curve and can take a while to fully introduce non-technical users to its functionality.

The software includes version control, container storage, issue tracker, grouping and goals. All of these provides great experience for a developer.

I don't like the interface, it looks too professional. Something more playful would be highly appreceated.

The reason we switched to Gitlab is that we found that it offers more than any other git SAAS product in the market and it wasn't just a code repository. They have CI/CD for automation and automated Artifacts.

1. Stability of the product was not the best, we had frequent hiccups where the pipelines runners were down or other parts of the system.
2. Pricing plans are pretty steep so it is 4x whenever you move to the next plan.

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.

GitLab is an easy to use and versatile project management tool. As a team, we use it not only for software development projects, but also for the follow-up of our other projects. It is really great that it is customizable, you can simplify your interface for your teammates who cannot use complex applications. This offers you a more user-friendly product.

It's a little harder for people other than engineers to adapt. You shouldn't expect traditional drag-and-drop kanban boards. It's a bit of a technical product. But if we consider that the intended use of the product, this is really normal, not a big minus.

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.

I have used GitLab extensively for several projects, and I must say that it is one of the best Git management tools available in the market. GitLab is an open-source, web-based Git repository manager that offers a wide range of features that make it an ideal choice for software developers.What I liked most about using GitLab is its comprehensive set of features. From managing repositories and branches to automated testing and deployment, GitLab has everything a developer needs to manage their Git workflow in one place. The platform provides features like continuous integration, code review, issue tracking, and project management, making it a complete DevOps solution.The user interface of GitLab is very intuitive, and it makes it easy to navigate and use the platform. The platform also has extensive documentation and a large community of users, which makes it easy to find solutions to any issues that may arise.

What I liked least about using GitLab is the steep learning curve for beginners. The platform is feature-rich, which can be overwhelming for new users. Additionally, the setup and configuration process can be time-consuming and may require some technical expertise.

Full suite of tools including but not limited to repository and issue tracking, milestones & issue boards, group and user management including project and even branch level permissions, continuous integration, scheduled jobs, project wiki, etc. All the features work together and using it to manage projects tends to pulls the details together rather than fragmenting them across different spaces.

The general workflow is similar enough to Github that most developers find it familiar. In fact there is probably feature parity or beyond, so other than needing another account there has never been much resistance to adoption among our developer team. At the same time the interface well designed enough for non developers to figure it out and stay involved as well.

The setup and update process is somewhat cumbersome on bare metal (probably easier using dedicated virtual machines and/or their omnibus package). There are a lot of dependencies and assumptions about the environment that make it much the most dreaded package to upgrade on my production servers.

It does kind of make assumptions about workflow that don't hold true for all projects. While it is flexible enough to adapt even when using only a subset of features on a project, it can leave people a little confused and overwhelmed because all the other unused bits are still around in the interface.