Gitlab Reviews

Gitlab is well suited for any project that requires revision tracking along with collaboration with other contributors. It supports the standard features of Git and adds its own recipe to the features that other Git SaaS providers offer as well. This includes issue tracking, pull request management (or merge request management in Gitlab speak...which I actually prefer considering the action that takes place), and recently artifact and package management. Gitlab has also been a leader in bringing CI to the repo ahead of its competitors. Of course, not all of these features need to be used. If all a dev needs is to track code, Gitlab can handle that just as well as any other cloud or self hosted repo.

Gitlab is well suited if you're looking for a cheap git source control provider with decently priced CI. However, it does lock you into using their build machines - in contrast, GitHub plays a bit nicer with external build services like CircleCI and Travis. However, Gitlab provides a fairly decent set of features; it is catching up to GitHub in a variety of ways.

Gitlab is well suited for distributed and centralized teams. It is less appropriate for agile teams.

Gitlab it's needed if you are developing software, and you want to enhance your development with integrations and automation.

For modern software projects, this tool is one of the best solutions for essential must-haves. It provides basic issue-tracking, ticketing, repository, and pipeline functions. From small to highly complex software, from single player projects to multi-level software building, this tool has nearly everything you need. Easy to configure and use, has a lot of best-practices already built in, easy to use, and shortens unnecessary devops scripting to a minimum as well as providing a very useful central repository for your code just as git. It expands git functionality greatly.

Gitlab is well suited for those that have a familiar experience with CI/CD, and can get their way around their source code repository. We have encountered some issues where it has started to slow down a bit, but we just gave the VM more resources.

If you have small or medium projects, go ahead and give a try on Gitlab. Two years ago, we changed Jira to Gitlab. We exported the issues and repositories into Gitlab. The Scrum Master is happier in using these tools because he always says that Gitlab is easier and less complex than Jira.

Gitlab is extremely well suited for an enterprise VCS solution. It's also great for personal projects as well. Best part is: it's free up to a certain point which allows you to properly evaluate the solution for your organization.

It is really suitable when you have a large team developing a number of scripts. It's easy to merge everything together. Everybody can access everybody's codes. Really speeds up the development process. Very useful for version control. It can get a bit difficult for a newbie to access it from the terminal. But once you get hold of it, it's easy.

Gitlab is pretty well suited for scenarios in which you want a more robust and solid codebase. The reason for that is they provide right away and with free plans too, continuous integration and continuous deployment services.

I wouldn't consider it too suited for open source projects since the community is smaller in comparison to other platforms like GitHub.

Well suited for source code version management, where the lot of people are collaborating on code across organization. Give visibility of code to the people who are participating in code commits, by code reviews, merge approval process.

We would whole-heartedly recommend Gitlab for code versioning with teams across different organizations as the management of users and groups is so easy. CI/CD is built-in and batteries included and because the implementation of Gitlab is standard it is easier to use than Bitbucket. If your organization is already in the Cloud Gitlab is one of the easiest solutions to roll out on AWS, DigitalOcean, GCI, Azure, Linode, etc. Even the management of Gitlab itself can be versioned and deployed using CI/CD tools such as Jenkins.

GitLab has a full suite of tools including but not limited to repository and issue tracking, milestones and issue boards, group and user management, including project and even branch level permissions, continuous integration and scheduled jobs. All the features work together and using it to manage projects tends to pull the details together rather than fragmenting them across different spaces. The general workflow is similar enough to GitHub that most developers find it familiar. It's replaced GitHub in our organization and we haven't looked back since using GitLab.

Gitlab does a wonderful job when it comes to implementing CI/CD in a project. Once tasks are set up, they can be used by developers to push code in production making it a really easy tool for day to day operations. It also has amazing source control features which are not just limited to code storage, but teams and individuals can access the code repositories.

Gitlab is a natural evolution after a certain threshold is met in most organizations: either projects become more complex in scope, additional team members add more 'noise' to a project, or there's just an extensive amount of space or security needed. Gitlab is a reliable next step after using GitHub: it functions very similarly, and offers consistent up-time and usability (especially important if working for a remote team). The project management is a huge plus for Gitlab, and has made it managing and deploying elements of a larger, complex project less complicated.

Gitlab is great for small companies looking for a cheap solution for hosting a large number of private repositories. It helps if you have experience with dev-ops tooling, as you may have to build some third-party integrations you would otherwise get out of the box with GitHub. It's also great if there is a possibility you would wish to migrate your repositories to a self-hosted network.

If you're an independent developer or organization whose main goal is to build a community around your open source projects, I would recommend choosing GitHub over Gitlab as the community is much larger and involved over at GitHub.

When we want to integrate different projects developed with work teams from different countries, it is perfect. It is not necessary to work physically in the office, with SSH security the code is traveling safely whenever and wherever you are.

Gitlab is suitable for projects with a limited budget and where there are technical staff available to drive implementation and set up (particularly where CI-CD is required). Whilst there are many integrations with Gitlab, they remain very technical and not very accessible by management and other non-technical team members. It is also not the most user-friendly issue tracking tool and does not contain as many features as other alternatives in the market

Gitlab is great in any environment where source code version is required. It is very similar to github.com with it's feature set but it also has a set of unique features such as build pipeline (we haven't used it yet). The features are constantly being added and they reflect industry's direction with features such as Docker integration.

GitLab is very well suited if you need to host private repositories and don't have the budget to pay for services like GitHub. GitLab is not very well suited for large open source projects. It's not as ubiquitous as GitHub and thus the user base on GitLab.com is much smaller.

In case you have many repositories and want some on-premise, Gitlab is the best thing you can get. For new startups looking for a great a great (or free) place to have private repositories, Gitlab is the best option you will find as well. It also has an integrated CI for your project, which is really nice.

Gitlab is well suited for internal development. We have not tried to use Gitlab with external outside the company resources.