GitLab Reviews

We have a normal use case to build source code and our agenda and then try to deploy it. The deployment is not specifically automated, it is semi-automated. So it is normal. We create an artifact, try to build it, and then deploy it onto the application server. It's not fully automated. 

At this point, I think the features are declining. 

We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people. 

There could be more features in GitLab, but we are as of now not using the full-fledged feature set. 

Another good feature is the code review, which also helps us with peer review. It helps in giving part of the code and giving back whatever the branch that the developer is working on. It can then be merged once it is thoroughly reviewed. Those are certain things that I think are helpful from a developer's point of view. It provides or mandates quantitative code into the master.

We do reviews as I also work with some of the leadership teams. Leadership teams generally focus on statistics, metrics, or some sort of dashboard. They would like to have the ability to categorize these things. They would like to have a very high-level view. That would help. Someone who is not really a developer, but a leadership team. They are always interested in statistics or metrics features. That is something I would see imbedded into GitLab. That would help someone who is from the outside take a view and understand how qualitative the code is, because they cannot definitely dive in and look at the code, and they will not be able to understand all the details. At a high level, if they want to see and understand, at least they will have some confidence about how the projects are going on.

I have been using GitLab for two years. 

The stability is good. I never had any issues. Stability-wise, I'm comfortable with it. 

Scalability-wise it is very scalable as well. Based on the code volume, there is a scope for improvement. I never had issues with scalability.

Technical support depends on licensing. We haven't reached out that frequently because it is stable and we don't see any issues. I don't recall anything that we had any particular challenge that we had to reach out immediately to GitLab and then get the answer quicker at any point in time.

I wasn't here for the deployment but the deployment takes around 10 minutes. 

Only a few aspects will take close to five minutes. 

I would rate GitLab an eight out of ten. 

GitLab provides some sort of static analysis part. That is what I understand, but I never tried it. I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors.

We use Gitlab for CICD work. 

Git hosting has an integration with ACD which is why we liked this solution in the first place.

This solution could be improved by adding modifications such as slack notifications.

I have been using this solution for four years.

This is a stable solution. 

This is a scalable solution although the CICD may be tricky to scale. 

I have previously used Bit Bucket and Github. Bit Bucket has some issues in our country. At the time we had banning issues within our government and only GitLab was. Bit Bucket is too slow and we had to wait for five minutes just to enter the platform. 

Bit Bucket pipelines are not that easy to consider and it was harder to use than GitLab. Gitlab is also more customizable. GitHub is more expensive than GitLab and didn't offer CICD. 

The initial setup is straightforward. 

I would rate this solution a ten out of ten. 

Our company uses the solution to manage code, Wiki, and repository management for multiple projects on Truck It In. The solution helps us manage our experience with projects. We currently have twenty-two developers using the solution.  

We are in the process of executing the pipelines to use the solution for CI/CD. 

The interface is much more user friendly than competitor products. 

The merge request tool is very valuable. 

It is easy to perform code and peer reviews. 

Key features allow creation of well-presented Wiki that includes ideas, development, and domains. 

The solution should expand features to match other tools such as Coverity, Veracode, or SonarQube with its static code analysis tool so third-party integrations are not required.

There can be a lapse of fifteen minutes to a day when updates are pushed. We do receive email notification of upcoming lapses and push progress, so that helps.

I have been using the solution for eight months. 

The solution is stable with no failures or issues in the version controlling or epic creation processes. 

The solution is scalable. We can manage issues or epics, make Kanban with proper backlog, and move any processes with no problems. It is scalable in terms of managing our experience and using it as a project management tool. 

We have not needed technical support. 

The setup is straightforward with good user interface. Third-party integrations can be a bit of a hassle. 

We implemented the solution in-house. 

We use Spring Boot at the back end with IntelliJ for IDs. IntelliJ is a good tool that integrates our projects with the solution through a well-managed synchronization process. 

The solution has a better user interface than GitHub and Bitbucket. 

We also use ClickUp which is a great tool for managing tickets and stream planning. We follow Agile methodologies so ClickUp is quite helpful to us. 

SonarQube has a new integration with the solution so we use its static code analysis tool.

The solution is valuable for developers because it includes version controlling, pipelines, CI/CD, and integrations. When moving from the development side to the production side it is important to ensure that code is bug-free with no errors. We have less issues on the production side because we take full advantage of the solution. 

The solution currently requires third-party integrations for CI/CD so I rate it a seven out of ten. 

Because GitLab uses an education license for cloud, there is unlimited storage for each account, so it's very useful. It is very flexible and easy because you can store data on cloud.

GitLab should include more features because, during the pandemic, companies like Google introduced more features. The integration and storage capabilities could be better. This would be very handy for educators and students.

We used this solution at my previous company for a few years. They initially deployed it on-premises but fully migrated to cloud because all the data was not fully backed. We had around 500 clients and 500 accounts.

It is 100% stable.

I believe it's scalable. It is suitable, and there was no need for exploration.

We used a lot of technical support for standard settings.

It is subjective. I cannot compare GitLab with Azure because it is based on experience.

We had to read the manuals first before we could set up. The manuals are helpful for consultants as we needed their expertise to complete the setup. In addition, they can ensure there is no downtime.

It has a very good price and is good for general sidetracking.

I rate this solution a ten out of ten.

I am using GitLab for many purposes, such as CI/CD.

I have found the most valuable features of GitLab are the GitClone, GitPush, GitPull, GitMatch, GitMit, GitCommit, and GitStatus.

GitLab could improve by having more plugins and better user-friendliness.

I have been using GitLab for four years.

GitLab is a stable solution based on version control.

The scalability of GitLab is good. We can have multiple Amazon AWS enrollments.

We have approximately eight people using this solution in my company.

We use the support when we are doing integration. We have a blog where we can open a ticket and receive support.

The initial setup of GitLab is easy. If there is a server the implementation will take 30 minutes to one hour. In the case, there is no server, then we can install the Docker box with the related supporting office installation. This will take approximately two hours.

This is an open-source solution.

We are using this solution because of our client's requirements.

I would advise others to prepare the documentation for their team members.

I rate GitLab a nine out of ten.

We primarily use this solution for end-to-end CI/CD solutioning and deployment as well as infrastructure, architect and environmental management. In addition, we plan to use it for version control and SaaS solutioning and have heard it is great.

The SaaS setup is impressive, and it has DAST solutioning. It also has dependency check and scanning mechanisms. If we were using other solutions, they would have to be configured, and we would have to set them us as a third party, but GitLab is straightforward. GitLab is a single solution that helps us do everything we need.

The documentation in GitLab could be improved a bit. For example, their RBAC is role-based access, which is fine but not very good. It could also be improved a lot.

We have been using this solution for almost seven years. We are currently using version 15.2.1. We are using GitLab Cloud, and it is a public setup.

It is a stable solution, and we have not experienced any challenges.

It is scalable, but we need to pay extra costs.

The technical support is good, but it is available with paid solutions only. So we have to rely on their documentation or wait for community updates for the free tier or vendor solution.

It is a cloud solution, so we didn't have to do much. We just needed to create an account, and the solution was ready. It is gitlab.com.

I rate this solution an eight out of ten because it is a good tool.

GitLab is a platform that facilitates hosting, collaboration and version control. We also make use of its pipeline capabilities. 

It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience. 

We are currently using Atlasian Bitbucket, Jira and Confluence. Atlassian offers more products than GitLab. GitLab offers source control management, version control and collaboration between developers. Atlassian offers features on top of this as well as more integration points for developers.

I have used Gitlab for two months. 

This is a stable solution. 

This is a scalable solution. 

The configuration of Gitlab is straightforward. There is no site deployment of GitLab needed on behalf of the end user, especially if they are using the cloud version. 

GitLab's pricing is good compared to others on the market. 

If we compare the GitLab repositories to GitHub, GitHub has many issues since being acquired by Microsoft. GitLab is more independent and offers a better user experience compared to GitHub. Gitlab is easy to manage and is a good example of the Git-based collaboration tools.

I would rate this solution an eight out of ten. 

GitLab can be deployed on-premise and in the cloud.

GitLab is mainly used as a repository.

The most valuable feature of GitLab is the ability to upload scripts and make changes when needed and then reupload them. Additionally, the solution is user-friendly.

I have not explored the solution fully but the features that I have used have been good.

GitLab can improve the integration with third-party applications. It could be made easier. Additionally, having API control from my application could be helpful.

I have been using GitLab for approximately three years.

The stability of GitLab is good.

We have approximately 20 people in my department using GitLab and in my organization, we have approximately 4,000 people using it.

I have not used the support from GitLab.

The initial setup of GitLab is complex and could improve.

GitLab is an open-source solution.

I rate GitLab a nine out of ten.