I really like using Gitlab CI. We are building and deploying our applications using Gitlab CI mostly every day. It's very stable and fast. So that m overall experience is very good with Gitlab CI.

The working style of most of the CI/CD tools are similar in the background. The ones that has better UI and fast responses are making a difference in the market. Gitlab CI, by far has the best UI. The button clicks, flows and placement of the features are very well-designed.

I cannot say least but I would be happier if Gitlab adds more UI features in CI/CD level.

I think it's good that you can use it in basically the same way as GitHub, and that you can manage it by making use of your existing knowledge. Also, I think it's nice that GitLab has unique features that are easier to use, such as a feature that changes the display of the file icon for each file extension.

Using Git as a configuration management tool is already common sense (essential), but I think this software is the most used for remote (distributed) development. There are many cases where you install Git on each person's terminal and operate the commands, but if it is team development and you can't use an "external (public Internet) repository", it is better to set up and operate a Git repository with GitLab I think it will be the safest and standard way to use Git.

I guess there is no choice but to get used to it, but I would like to see more visual changes and expressions (messages) when conflicts occur that are easier to understand for beginners. After all, I'd like to see them develop an interface that makes it easier to understand the concept of Git configuration in the first place.

Not long ago, I ordered some GitLab licenses since more people wanted to use it. I asked to go from 57 to 75 licenses. Instead, GitLab put the order in wrong and added 75 licenses, bringing us to 132 total. About this time, I was pulled to a critically-important project that was way behind schedule and told not to work on anything else. When I got enough breathing room to switch back, [SENSITIVE CONTENT] acted like she couldn't care less. The most I ever got was "I'll be sure to look into it" or "I'm still looking into it". The process dragged on for weeks. I had to nag her over and over again for updates until she finally told me that GitLab's billing department had decided... not to give me a refund because it had been too long. How convenient, especially after dragging out the process for so long. I complained about this, asked for a new account manager, and got what I requested. [SENSITIVE CONTENT] took my concerns to the GitLab crew again... and got told once again that not only would we not receive a refund, GitLab wasn't going to offer us any sort of compensation or credit whatsoever. We're a software company as well, and we would never treat loyal customers this way - especially not our power users. I've built my DevOps career around GitLab and encouraged others to do the same. That GitLab could be so tone-deaf over a problem that was clearly their fault speaks volumes to how the company has changed.

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.

Its quite to easy to view stashed branch and some filter options in the repository. They can improve a bit to stay for the best in the market

At times , using the github & bitbucket in my project. This lags some feature which am seeing in the other repo cloud

GitLab has all the features my team needs for source code control and manegement. Very easy and intuitive to set up different group of users, projects, repositories with different levels of access. The GUI is also very neat and simple.

GitLab allows you to quickly set up an on-premise platform for source code control. Good integrations with CI/CD and very clean GUI.

Learning how to effectively use a versioning tool can be quite difficult for non-technical users.

I enjoyed working with GitLab, although there were a few instances where I encountered challenges understanding certain aspects. With all of its features, it really makes teamwork easy, and I appreciate the security measures it provides. The use of merge requests ensures thorough code review before pushing changes to the main branch.

GitLab's collaboration features, such as merge requests and issue boards foster efficient teamwork. GitLab places a strong emphasis on security and provides tools like role-based access control, Workflows and issue boards can be customized using the platform. The CI/CD pipelines at GitLab are strong. The ease of setting up and managing pipelines directly within the repository simplifies the development process.

Navigating the platform and understanding all its capabilities might require a learning curve for individuals new to the tool.

Overall it is a 8.7 out of 10 experience, considering the average to be 5. It is better than some of the platforms in many terms, but till lagging some level of scalebility.

It offers an all-in-one platform that includes version control, issue tracking, continuous integration, and more. It excels at managing Git repositories, allowing for easy branching, merging, and version control. It has robust access control features, allowing administrators to manage user roles, permissions, and project visibility.

It is resource-intensive, especially for larger projects or organizations. It is hard to initially learn the tools and technologies. The UI/UX is less tempting.

A safe pair of hands with great functionality.

Ease of use, clear and easy to use interface and tight integration with source code and continuous integration tools.

Remove continuous integration functionality when not needed appears to be difficult - but this may well be a user error.

Having our own git instance is a very good thing. We're know where our data is. (Self managed). Also, Gitlab have multiple integrations, and it is very great.

Most of our problems have been solved through the official documentation. But, we have some problems with performance that we're under it.

improved the quality of software delivery and develop DevOps in our company are resulled for adopting Gitlab

One of the best tools for improving SDLC and controlling IT project with fantastic CD

there is no mobile client or Windows client

GitLab is the code versioning system that our company uses on a daily basis. We found useful to have a fine-grained authorization management for your users/developers, that made it easier for us to ensure the only the right people can see the right things. We also use the "organisation" feature to have all our developers in the same place with the right access.

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.

It is such a great system. We use it daily at work and I integrated it into my homelab as well to keep change controls and ci/cd under control. It has made my homelab crazy efficient when I need to do things. For work it makes our daily tasks very easy to manage and it's much more integrated than having to build out all of the atlassian stack.

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.

We were trying to have a central hosted repository SCM system. For issue management we normally use Linear, although for smaller projects we keep track of issues using the integrated issue manager. The product integrates seamlessly in the development workflow, implementing and enforcing best industry practices onto all the contributors of the project, and allows for quick deployments to production and testing with its integrated CI/CD system.

GitLab is a great integrated SCM, Issue Management and CI/CD solution which is a pleasure to work with. The tools feel very nicely integrated and cooperate very well. It embodies by default the best practices for code management and is developed by a company which has open source and transparency at its heart, thus reassuring that the product can be trusted, either as a SaaS solution or as a self-hosted solution.

The SaaS version of the problem has over the year suffered some issues; however these have been decreasing over time and the company has made a hosted experience on par of those of other SaaS solutions. The resource consumption of the product is not to be taken lightly; however for small teams it has a relatively inexpensive monthly server cost.

Satisfactory! Started out on the free plan, and as the project grew and I needed more space and developers on it we upgraded and even got more access to more tools to better streamline our DevOps processes and overall project development.

Gitlab offers you a secure space to store and manage your git repositories, for personal use and or for your organization's development team. You can easily assign tasks to team members, and track and follow up on them with clearly laid out and categorized Kanban boards.

Gitlab's UI and UX are quite overwhelming for a first-time user. If you are new to Gitlab and you haven't used a similar platform like Github or Bitbucket before, you will definitely need a little training to fully utilize your Gitlab space. Make sure to get through the entire onboarding tutorial to avoid feeling lost because it's all going to seem very clunky and difficult to find your way at the beginning.

Despite my gripes with debugging and monitoring, GitLab is a mind blowing software offer with an unbelievable feature set for a platform that is effectively free for many setups, not forcing a subscription or pro features by crippling its basic product but by providing additional value for paying customers instead of extorting users for critical features.

The pipeline system is by far GitLabs most important feature, though the extensive offering of supporting services such as project wikis, hooks and integrations make it a flexible control center for all needs of software development.

Debugging pipelines seems to be less than an after though, with minimal support and no indication of being in anyone's focus. Monitoring seems like a lackluster proof of concept released to the public, with many issues being ignored for years and all around extremely poor support unless the only thing you want to do is monitor the default setup for the default metrics in the default view.

GitLab is my everyday tool which I use for my course project management. I am really happy with its simple and easy-to-use open source support.

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 has a large and active community of contributors who help maintain and improve the platform

GitLabprovides a complete end-to-end solution for software development, from source code management and version control to deployment and monitoring. This can be very convenient for teams who want to consolidate their development workflow in a single platform.

One potential limitation is the complexity of the platform. While GitLab's comprehensive feature set can be a strength, it can also make the platform more challenging to use and configure, especially for smaller teams or organizations.

GitLab is a great place to host git repositories - for both private and commercial use. With its pretty and intuitive design, GitLab offers a great experience to work with. Collaboration is managed in a really great way. Their pricing is also amazing: it's mostly free to use. We've had multiple private repos on GitLab for years now and haven't had any reason to upgrade to a paid plan so far.

GitLab's customer support team is really slow at responding to support requests. However, since I'm on a free plan, that's okay and I think they probably allocate all of their support resources to their paying users - and that's totally fine.

Very satisfied and will consider it also for the next professional projects.

The installation is pretty straight forward and easy. It's the only free git server solution I found that offers LFS support. We started our project without the support of Git LFS but as the project grew, we had to find a solution and transfer our repository to an LFS ready server. GitLab offered the perfect solution, allowing us to keep our existing SSH keys for authentication, existing LDAP users and transfer our existing project pretty easily. Since then, we never ran into issues and the server is running smoothly since the first day.

The server is based on RoR so it's heavier than a simple Git Server. You need to make sure you have enough resources to get it to run properly.

The overall experience was good. It's highly recommended for companies who want host their code in their own infra and are ready to maintain the code hosting software itself

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.

Overall, GitLab is a good for development. Most commonly used features such as MR and code review work very well on GitLab. The best feature on GitLab is CI/CD, it has everything you need to build an automated pipeline, from build agents to container registry. However, the exploration feature is not as robust as other services and there is still a lot of rooms for improvement.

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.

Overall, GitLab has been a really solid addition to our workspace. It allows us to collaborate much easier and gives us the opportunity to add tests and validations in our pipelines so that whenever code is deployed, it can be checked for quality assurance and take the appropriate actions based on the results. The amount of features GitLab is packed with, it may be a while before I am able to learn it all but also be able to make use of it all. I will say this however is that whenever I do learn something new, it is often a welcomed change and either myself or my team is ecstatic and excited to not only implement the newly discovered feature, but also to reap the benefits of the sweet update or enhancement! Great job GitLab, cheers!

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 has been a great asset to my development toolbox, and I'm glad to have it.

GitLab has been a great resource for me as a developer, providing a user-friendly interface and lots of documentation for assistance. I can collaborate with colleagues, keep track of code changes, set up repositories and branches easily, and track issues, bugs, and feature requests, all of which help me stay on top of my projects.

Although GitLab is a great platform with many powerful features, it can be difficult to use and understand for those without much experience with version control systems. The UI can be confusing, and the language can be overwhelming. Additionally, there have been reports of bugs and other issues which can be disheartening. Ultimately, GitLab may not be the best choice for everyone.

Overall I have enjoyed working with GitLab. Our build pipeline was very customized so that it matches the exact process we wanted, and when there is a build issue, the problem is easy to identify and correct. The UI is a bit cluttered and unintuitive but it just takes a bit of extra time to get accustomed to.

Gitlab has been a great collaborative tool for us which allows for very customize-able build pipelines and easy issue tracking. The ability to add comments to code snippets and open up un-resolved threads allows you to stay on top of suggestions. Having to manually resolve those threads on your code comments before merge means that you are unlikely to accidentally push code forward without addressing those suggestions. There are also a good number of settings that allow you to control options such as how you want to handle merge commits, giving you complete control over your repository.

The main issue I have with GitLab is that the UI can be confusing and unclear. I am not a fan of the stacked diff view when comparing code changes. Compared to another version control system like BitBucket, I find it a bit more work to sort through the changes in a merge request. It's something you get used to, but initially is a bit unintuitive and less enjoyable.