Opiniones de GitLab

Muy facil de organizar, permite subgrupos

Version en continuo cambio, equipos limitados a 5 personas

GitLab , tiene grandes potencias de informes y análisis de trabajo requerido en cuestiones de seguridad de datos , nos a aportado mucho beneficios de herramientas útiles para mantenerse seguro te n nuestras tareas.

Maneja algunas herramientas en la API que no ejecuta en la automatización de nuestro sistema. Pero se a permanecido estable en la seguridad de datos.

Lo que más me gusta de Gitlab es que puedo crear un servidor privado y así me aseguro de tener el control de mis datos.

En general todo está bien con GitLab, pero si tengo que mencionar algo sería la de optimizar las imágenes Docker para que no demanden muchos recursos.

Lo uso a diario desde que empecé mi carrera profesional. Gran facilidad de uso, creación de tickets y de progresos, ramas...

Al principio, si nunca has utilizado una herramienta de este tipo puede ser un poco complicado hasta que te haces a ella, la implementas en otros softwares...

Me resulta muy útil en mi día a día, desde que lo hemos empezado a utilizar hemos optimizado el trabajo.

No hay nada que no nos guste por ahora sobre su uso.

Developers like it and you can use labels to make it work for task management, to some extent. Facilitates proper code review and collaboration in merge requests.

Reporting functionality is limited compared to competitors. Would recommend it for development, but not for task/project management. Not that user-friendly for non-techies and requires a lot of customization to make it usable for sprints etc.

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.

GitHub charges for company use, and my old company wouldn't have paid for SCM no matter how important it was to our department. Thankfully, GitLab installed just fine on a VM we spun up internally, and that was all we needed. Our Git repositories, client websites, and configuration files had a home. I can use the Git CLI, and there's a convenient web interface and hooks for everyone else (including me when I didn't want to use the CLI).

Setting this up internally is a hassle. You need a VM and a valid SSL certificate, which is a fairly low bar for entry, but more than most products. Also, it does update fairly often, which I suppose is better than it not updating at all.

GitLab is most trending software in IT industry to manage the code management very easily with more secure one.

On my opinion the UI was not user friendly as I was using for a year I feel GitLab somewhat hard for new users other that that every thing is good

I liked Realtime code collaboration the most. And Version Control

It doesn't have open source support like GitHub. Also documentation should be more elaborative.

How it allows the workspace to become more effective and fluid.

Do not have complains so far, and I believe that's a good sign.

I love the UI, the instructions and documentation

I have no negatives on its usage and features

GitLab allows users to easily store their code projects and files in a safe and secure environment, allowing easy collaboration amongst users.
You can import repositories from other Git tools (such as GitHub) with ease, GitLab also imports any version history and accompanying branches.
The ability to make certain repositories private is excellent, most similar git systems charge extra for this service.

The user-interface, though clean and responsive, can be hard to use and master. Especially for new users, training is definitely required.
The integration with interfacing tools is lacking, most systems (such as GitKraken) require a premium license to connect with GitLab.
User management can be complicated, as the user interface isn't particularly clear here, and the different levels of access aren't clearly identified.

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.

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 CI is by far the most valuable feature of GitLab. Travis CI was the first one to offer a YAML-file based build system - but it's GitLab CI to make pipelines very flexible and expressive. While Travis was okay for most popular languages in open source projects. GitLab made it possible to run enterprise-grade pipelines with many stages, each having multiple simultaneous jobs. This, plus git repository, Docker registry, and several other tools, making it a complete solution - starting from an early development cycle, through build, to deployment and monitoring thereof.

Several pages perform bad, e.g. pipelines list in big projects. Some pages don't have search and sorting. These are minor issues though.