GitLab Erfahrungen

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.

GitLab is a valuable platform, especially for decentralized software development, as it is easy to keep track of open issues and discussions very similar to what you get with GitHub, with the benefit of being open source and selfhostable.

The interface may be overwhelming for some users and requires some time to get used to, especially if you're new to GitLab. In regards of UX, GitHub is quite a bit easier to get used to.

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.

Gitlab offers excellent user friendly interface and has literally no learning curve. I love how its script is well organised and easy to develop. It supports docker for each stage, which creates us a stable environment for the builds and tests.

I cannot think of cons in Gitlab. Only thing is that the pipeline is just developer friendly, we could really use a interface to design the pipeline for non-programmers or new comers.

GitLab is easy to use and makes processes and collaboration with colleagues a breeze!

There really isn't much not to like. I've used several other version control services, and GitLab is right up there with the best of them.

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 appreciate the user-friendly interface and ease of use. The convenience of quickly creating and managing repositories as well as collaborating with others is a plus. Furthermore, the integration with other development tools such as CI/CD and code reviews makes it a comprehensive solution for teams.

Documentation for build/pipeline processes related to CI/CD could be improved by providing graphical user interface (GUI) tools that are compatible with all major operating systems.

Can use for free in the beginning to test it. Can be used on most devices with internet connection.

In the beginning the interface is difficult to understand but with practice and with enough time it becomes easier

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.

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.

- Excellent UI that is easy to understand: many of our developers are migrating for the first time from other software (github, bitbucket) and a constant comment is that the ui is intuitive and easy to understand compared to previous software. The transition is always smooth.
- Feature-full product: Gitlab offers a variety of features that I have found to be excellent and of high quality. The code-review process in gitlab is always smooth with the ability to resolve or re-open discussions, address specific comments or the whole of the discussion, the ability to suggest and even apply and commit code from the ui is also a huge plus. The IDE is decent and the file editor is also decent. The CI/CD integration with gitlab runners is smooth, the notification system is great. I get an email whenever a test fails. All from the gitlab ecosystem, i do not need to go to circleCi or some other provider for all of this, which allows the ui and experience to be consistent.

At this very moment there is no feature or issue that I have found to be detrimental to my experience.

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.

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.

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

Gitlab really made my life easier when dealing with software development. Its features such as software versioning, project management and time tracking are very usefull and allow even big teams to cooperate smoothly and easily.
It is fast and intuitive in almos every feature.

Some things in project management are not perfect, such as issues filters, that sometimes mess up a little. For example, setting filters and copying the url not always results in perfectly re-setting same filters when navigating to that address.
But these are ordinary small bugs that do not affect the overall good quality.

The biggest pro for us at JeFawk Games (me and my freelancing friends, not employees as stated) was the fact that it allowed for 1GB of space for free in private repos! Since we're working on games, we really needed the space and the privacy. This was from before GitHub was acquired by Microsoft and gave away unlimited free repos.

Time forwarding a bit and GitHub is giving out free private repos of max 1GB with the option to use the Large File Storage thing, which in GitLab you don't need to bother with as you get it by default.

It includes DevOps and a lot of other features that frankly we don't make use of.

It's just the much bigger space by default and up to 3 collaborators. GitLab is great! Although it does have some cons....

One of the biggest problem with GitLab is that their website is a bit laggy. You can wait 1 to 4 seconds for some pages to load.
Another issue is that we actually use the GitHub Desktop application to handle GitLab repositories and the setup to connect the application to GitLab is kinda clunky, more like to allow GitLab to be grabbed as URL. Wouldn't wanna go through that again, hopefully they already streamlined it as last time I did it was about 2 years ago.

1. Free of cost
2. Highly efficient, does the job without uncertainty.
3. Never observed any downtime
4. Very frequent and proper updates to the software.
5. easy to maintain
6. can easily integrate with jenkins for Continuous Integration- Continuous Deployment.
7. Easy to setup and use, no support or setup or external teams required. Anybody with minimum computer skills can get this up and running.
8. easy integration with youtrack for issue tracking and merge requesting tracking

These are not very big cons, but I find them annoying and could definitely use improvement:
1. The edit description on an open merge request also shows up on the history. So If somebody were to make a 10 different changes to the title while keeping the
2. The code formatting in the description box is not too good. It can take several tries before getting it right.
3. There is no way of searching for something based on a line of text. For example if you were looking for a commit or a merge request but you only remember the
4. sometimes very challenging to go back and undo merges which are quite complex.
5. on a given pr, it shows icons of all the participants but doesn't say which participant did what... for example if 5 people have just viewed a pr and done nothing else even then it shows all of them as participants. It would be nice to have a feature which will only show activity by participant on every pr.
6. text based Search via ui is practically no existent. So if you search for something using a text which is part of a commit message, chances are it will not show up 100%.

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.

GitLab has all the must-have features for complete development and deployment flow.
The easy-to-configure pipeline is a differential, mainly due to the possibility of installing the agent (GitLab runner) in our infrastructure.
Issue management and merge requests are excellent and do not fall short of your direct competitors.
I use the GitLab in the cloud (SaaS) and on-premises, and it supplies my DevOps needs and team collaboration on the code review process.

On bitbucket, it is possible to see in realtime when a coworker is reviewing the merge request (pull request). It would be great to see this feature on GitLab too. The Runner registration is a bit harder when using an automation like Ansible.

Gitlab has an extremely robust free tier with tools that go far beyond simple source/version control. We use the Gitlab CI/CD pipeline runner extensively, allowing us to not only use Gitlab for source, but also for our deployment/build pipeline. Gitlab also has the ability to manage Kubernetes clusters from the suite, which is super helpful. We also extensively use the issue board for tracking scrum issues, which includes time estimates. Gitlab used to be most popular for offering free private repos, and it still does, but these other free features make it an absolute home run. We use Gitlab for every project because of how great it's been.

The pipeline runner can occasionally be a bit buggy sometimes, but nothing critical. For example, if you prematurely stop one pipeline and immediately start another, it can take 10 minutes for the new pipeline to start for some reason. Also, the time tracking on the issue board does not automatically put the sum at the top of the column, which I find annoying - we built a small gitlab api integration to pull that info for us. They have been updating this feature recently, though, so it may be solved soon.

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.

The integrated CICD is what makes this stands out for me.
The .yml configuration is powerful enough to access your servers from gitlab making every push you made build automatically.
Deployment Keys, Access token, its just way more powerful than github and much more UI/UX Friendly than Bitbucket.

Its also note to take that the pages are lighweight, you hardly ever feel the loading time. More top of it it's free.

While the git related features are astounding I feel like the Issue trackers are way more clunky to me.

The board is quite nice, you can drag items of it to different board categories, however. the lack of sub task for a task is killing me.

Suppose we have a feature task, I'd like to put a mini sub task under it so i can track all of it on one parent task. Just like how you can do it on redmine or asana. One thing that github is superior to gitlab is this area.

We use it to collaborate with the development and QA teams.

It's quick to create a ticket, measure time and sort the type of work from tags, and send it to the colleague who will do that work.

What is interesting is the grouping of several teams in a single project, without interfering with each other's issues.

What we used most was the drop down chart. The rush that it imposes, makes us work faster to try deliver what we plan, as the deadline get closer.

It is very chaotic visually, lot of functions are hidden in menus and submenus, I know that developers love it, but it didn't work in my team.