GitLab Reviews

I love the Boards for tracking Issues in their life cycle. Customizable Columns and Labels make it quick and easy to see where an Issue is, giving a high level for management and the rest of the team, while having all the details and attached code branches and merge requests for the developer and stakeholders. I love how it's able to connect code from several projects to Issues, no matter where they live, so you can have as many boards and projects as you like! It's well put together and seems natural with everything I try to do organization-wise. Integrates really well with developers' workflows.

GitLab is always improving and enables you to request features, so if you want something, suggest it and they'll get to it! Sometimes that's a bit slow, but you can usually work around it.

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.

Flexibility. You can either go Cloud, or setup your own GitLab infrastructure. With GitHub you can, but is not that simple. Also, the Pipelines are way more polished that GitHub Actions, which lately is having major issues. Plus, Pipelines let you easily reuse the CI code. Also, you have a Community edition.High Availability is a key feature to take into account.

Although it has a lot of integrations with 3rd party services, it lacks of having a Marketplace, like GitHub has.

GitLab does well as an all-in-one software development platform.

If GitLab makes a billing problem, it may refuse to rectify the problem as they did with us.

The fact that I can deploy Gitlab locally and start collaborating with my teammates on version control and source code management.

sometime the application becomes bit laggy and crashes

Every part I have used has been incredibly efficient: creating issues, assigning tags of varying priority, assigning the task to a user, editing issue descriptions and comments.

While not hugely important to the functionality of the software, when adding a description to issues, since the language used is "code-like" it can be difficult to get a sense of how the description will turn out once saved if you are a user that is not well versed/comfortable with coding. It would be nice to present screenshots pasted and view bolded characters etc.

It is a good option for corporate companies as it is an open-source code repository that is widely used for developing and managing code

Gitlab does not provide us with an option for different authentication apps the UI and response also feel slow at times

Very easy to manage any source code with the push and pull features and you can integrate it with many softwares which can make the process even easier. You can clone any repository and work in parallel with your coworkers which makes the work faster.

A little bit confusing when there’s any merge conflicts.

i love Gitlab, it is the best in the game and can be either very simple or very complex if you need it to.

I mostly like everything, but I would add an easier way to commit your changes directly through gitlab, also create and edit branches.

what i like most about gitlab is their functionality of runners which are very fast interms of achieving ci/cd pipelines.

what i like least is it is not opensource and has in built subscriptions for usage

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.

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.

GitLab is an awesome tool to use everyday. It is simple and easy to install on premise. The free tier is enough for any small business / team.

What really makes GitLab stands in front of the competition are its awesome CI/CD workflows. GitLab CI is incredible, you can do anything you want with it from building your sources, checking your code quality, deploying your projects... It is possible to make connections between various pipelines and have multiple repositories connected together to build your final "big" project.

Even if GitLab is simple to use, it's a big piece of software that can sometimes become slow on the web user interface.
Moreover the review system is sometimes not so easy to use compared to other competitors. Hopefully their are great browser extensions that solves this issues.

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.

Gitlab has features to set up project wiki, deployment, CI/CD pipeline and managing the project with role management with adequate space for personal projects.

The documentations are bit confusing and third party plug in integration is bit difficult and confusing.

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

It is a great tool to use for creating a baseline for source code management, versioning, and backwards revision history. It is possible to apply branchin strategy as you wish. We used it in our DevOps & Automation activities with entegrating a bunch of other tools.

Sometimes it is very difficult to manage the conflicts in the merge requests coming from different branches to the main branch specially if a lot of developers working in parallel.

Gitlab is my primary source code management platform where I store the repositories of my applications. It's very powerful and easy to use. I really like the CI pipeline because easy to configure and provide the automation you need in deployment. Code review process is also very nice.

All the things I need for my daily usage are covered. Would be nice to have an out-of-the-box dependabot integration without having to configure so many things.

I use the GitLab Community Edition (CE) and the first thing I love about it is it's Open Source! I am a believer of Open source software! In my company, we host our own instance of GitLab CE and it's been smooth. We use it for source code hosting and for CI/CD. Source code hosting has been great. CI/CD is nice too. GitLab has all the features required by a code hosting software - groups, groups within groups, repos, role based access control for members. Members can also be grouped with names - helpful to create a group for a team and add members to the group and give access to the team/group. It has forking, SSH/HTTPS git repo access, Notification/Watch repo features. It also has lots of integrations. We use slack a lot and we have integrations with slack which GitLab provides, and we have configured it to get notified for different things, starting from commit pushes to pipeline failures. We also use the GitLab pages for hosting the Wiki site for repos. It's pretty neat! The GitLab CI/CD has the concept of runners which run the CI/CD tasks/jobs. Runners have tags, and you can easily use the appropriate tag in the config to run the task in the appropriate runner. We use different runners for different things like, pushing to a Docker registry (requires special permissions), accessing a prod DB/application, running normal tasks (scripts) etc. All in all, it's quite good

Although GitLab has lots of features. I do have some complaints about it. I hope that newer versions will make my complaints obsolete! Starting with the CI/CD, it's quite good. But it lacks some features and flexibility which we expect in the upcoming versions. Features like one CI/CD pipeline triggering another pipeline (not present in CE, not sure about Enterprise Edition) and things like grouping jobs in a stage. Also, the CI/CD UI is not very good. It has glitches, there's no auto refresh in all the UIs to show the status of a job - if it's successful or if it failed. The job UI also isn't very great, like, if the job names or stage names are big, it becomes tough to read. Also, when the job log is very big, it reloads the page when the job finishes and truncates the output of the job and makes it available for download instead. This can be good or bad, based on the use case. For us, it was mostly not a soothing experience.

I started using GitLab for an external project and I like the following:
1) Easy to work with and auto explanatory. Creating/configuring a new repository is really easy.
2) Great CI/CD implementation. Having the repository with built-in CI/CD is really convenient, you can have everything related to the build and deployment process saved along with your code. I have used bamboo and I really appreciate this feature, it might have its problems but it is really useful.
3) Unlimited private docker registry, you can have your own private registry for free. I cannot express how useful this is.
4) In order to help with the CI/CD process it allows the creation of tokens with access restrictions (read only), so you can use these tokens to download your code or your docker containers without having to provide your personal credentials.
5) It has its own task manager
6) It has free agents that are in charge of executing your builds/deploys so you don't have to provide your own resources.

1) Configuring build variables is really messy and it is not an ideal implementation. I haven't found a way to set different values for them depending on the branch, so configuring different environments is not too easy
2) Even though having your code with CI/CD is really convenient, it has some drawbacks. If you have an established continuous deployment process that you repeat in many projects and you want to change it (maybe a fix it or improve it) you will have to add that change to all your repositories and all the branches that you want to deploy. So it is a really good feature but it is not too flexible
3) The task manager is messy, and I didn't find a way to have a shared board.
4) It does not have too many software integrations, as I mentioned before I have used bamboo and I really like their integration with other software

A huge number of features.
Intuitive and easy to use.
Extensive documentation and good customer service.
Flexibility of customization.

It can become expensive, particularly if the company has many users.
Some less-known external tools cannot be integrated.

I believe this is the best Github competitor which offers more configuration flexibility in setting up your development lifecycle.

The menus are not very UX friendly. There are lots of options when using Gitlab and sometimes is hard to find the particular section you need. It's annoying but having in mind all the good things that Gitlab offers, it's negligible.

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.

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