Gitlab Reviews

Gitlab is a great opportunity to "practice what you preach" if you are a shop that advocates the use of open source tools. Whether you use [Gitlab] or your own internal deployment, this tool offers good value for money (typically free in both cases for most organizations' needs). It would be less appropriate when an organization:

1. Doesn't want to host their own revision control, for less hands-on DevOps
2. Needs their code to be private/proprietary, and
3. Already has existing products and workflows for Continuous Integration and project management

In this case, a company license for GitHub.com may make more sense.

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.

In monitoring and safeguarding the development, maintenance, and deployment phases of modern software, web and android applications, Gitlab works wonders. The data is in a safe place, and it is easy to go back in time and create branches to test different code optimization strategies.

If you are looking for a secure, agile, custom deployable SCM solution for Enterprise applications, this is the one for you! However some features like the ssh key integrations and other 3rd party integrations can be improved.

For most project scenarios, Gitlab is a solid choice to manage your code. While there are plenty of free platforms out there to give you a git repository, Gitlab particularly shines by providing gated merge requests for you at the basic paid tier while others require higher levels. The code review interface is more sophisticated and makes it easy for you to start a code review without necessarily doing a merge right away through a single checkbox. The code review templates were particularly powerful for us because it allowed us to provide custom documentation and a checklist to remind the developers what needed to be done. The custom fields can't prevent a merge programmatically, but it makes for a good user flow.

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.

I like it a lot. To me, it feels very simple than other systems I used in the past. Version control is not something easy and they make it simple and easy to use. The whole experience their platform provides is just great.

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.

I will admit, being an enterprise Gitlab user may come with additional access to Gitlab support. With that said, I have found them to be very supportive and responsive when prompted with questions about the tool. The engineers I've worked with have been very keen to listen to feedback from my team and have taken it back as suggestions for improvements to the tool.

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.

If you like an all in one package where everything is stored in one place, Gitlab is a good option because it already comes packed with a lot of features at half the price of a GitHub subscription. Also it's particularly well suited for devops.
I wouldn't recommend it for open source projects though as not everyone knows about Gitlab.

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

I've never used Gitlab support.

I think gitlab is really easy to use but they still have way to improve the UX of their interface

Well suited for small to large teams where continuous integration is a requirement.
Less suited if the team is not inclined to research out the specific scenarios which they might face later on when the setup is done.
A thorough R&D in the documentation needs to be done before setting up the cloud/self hosted servers.

It's a solid product and its only real competition is GitHub. (Don't even consider Atlassian's offering here, GitHub and GitLab are both miles ahead.)
You're going to need hosting for your source code, and Git is likely what you'll use, therefore you have 3 serious choices:

1) Self host. I wouldn't recommend this.
2) GitHub. If your project is open source, you should use GitHub. The experience will be worse than GitLab, except you will be most visible to the open source community. If only part of your project is open source, you might consider hosting your whole project in GitLab and mirroring the open parts to GitHub.
3) GitLab. If you don't need GitHub's open source community, then GitLab is 100% your choice. It has a stronger, less buggy, cleaner, more featureful experience for working on code with a team.

So at the end of the day, you're likely going to be using GitHub or GitLab. Think about their missions:

GitHub: Community First, Developer Experience Second.
GitLab: Developer Experience First, Community Second.

Which one aligns with what you want? For most of you: GitLab. For the Open Source projects, GitHub.

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.

At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft.

In some ways, as mentioned before, the web interface can be a little different to get used to. The gitlab documentation is also a little lacking compared to documentation of other tools in the same class.

GitLab is very good if you want to self-host your instance, and it integrates well with Azure AD. I would suggest using this if you want to do everything in GitLab end-to-end, from setting and configuring (DevOps) to security dashboards to sprints to development to code reviews to deployment to even rollback. GitLab is really very powerful and configurable, would suggest to trial it out first and see if it meet your needs.

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.

We haven't had a lot of reasons to open up support tickets, but when we have, Gitlab has addressed our issues. So I am pretty happy about that.

Gitlab worked better for our team when compared with GitHub. There was better control over resources when we hosted the system locally, and users could be managed easier. Being a small team, we didn't run into too many issues. However, the UI for managing user access control could be improved.

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

The support is agile and respects the time of SLA. This regarding the Starter license. Surely for higher-level licenses the support is even better.

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 easy to use. It's a ready to go software.

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.

It is a great product and serves its purpose.

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.

I haven't contacted customer support because I haven't had any problems with Gitlab. Their service has been outstanding.

I know they have a very active Twitter account in which they provide very quick updates. As far as I know the community is pretty happy with their service.

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.

Faster resolution of tickets, easy to work with support people

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.

The web console management is superior and I would have given Gitlab a 10, but sometimes it is hard to find documentation about a configuration setting in the gitlab.rb configuration file. As we move everything to code that means moving our CVS tools to code as well - and Gitlab to code. The usability of Gitlab from the end user's perspective is superior and the usability from the operations team is very good and getting better but there could be a little improvement in the gitlab.rb config file layout and documentation.

The online documentation is best in breed and sets the example for all other platforms. We find it so useful that we have never once had to reach out to the Gitlab support team for assistance. In fact, because the chef recipe is so well written we have found that most issues are resolved with 'gitlab-ctl reconfigure'.

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.