We are using GitLab for source code configuration and for CI/CD processes.
Ubuntu 22.04 for GitLab with maintenance support by ATH
ATH InfosystemsExternal reviews
External reviews are not included in the AWS star rating for the product.
Optimize coding processes with efficient CI/CD while exploring AI integration
What is our primary use case?
What is most valuable?
The CI/CD process is very efficient. We are utilizing the pipelines extensively and gaining significant benefits from GitLab.
What needs improvement?
We are not using the AI process yet, however, I would like to see AI support in GitLab. Maybe it already does. I am not sure how it supports AI processes.
For how long have I used the solution?
We have been using GitLab for two years.
What do I think about the stability of the solution?
GitLab supports us very well.
How are customer service and support?
We do not have any direct technical support from GitLab. We ask questions to our IT department, and they may seek external support if needed.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
What about the implementation team?
The initial setup was handled by our IT department.
What was our ROI?
GitLab is a cost-saving tool and is particularly effective for coding processes.
What other advice do I have?
I do not have any recommendations or suggestions. I rate GitLab a ten out of ten.
Boosted productivity with automated pipelines and seamless collaboration
What is our primary use case?
I use GitLab to manage our development lifecycle. We use it to store code and automate our CI/CD pipeline. Once developers commit their code, the CI/CD pipeline automatically starts, supporting development through various stages. It is part of our software development life cycle.
What is most valuable?
What needs improvement?
There are some challenges with repository file management as GitLab may struggle to manage larger files. Improvements could be made regarding size management and file partitioning.
Also, the UI has remained the same for a couple of years and could benefit from an update with AI features and better customization.
For how long have I used the solution?
I have been using GitLab for three or four years.
What do I think about the stability of the solution?
I have not encountered any performance or stability issues with GitLab so far. It has remained stable and reliable.
What do I think about the scalability of the solution?
GitLab is scalable as multiple users can simultaneously access it without issues.
How are customer service and support?
We have rarely needed to escalate issues to technical support since GitLab usually runs seamlessly. Occasionally, issues might arise if the URL isn't up or due to server problems.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have worked with Bitbucket. In comparison, GitLab is more advanced, particularly in terms of cloud capabilities.
How was the initial setup?
Setting up GitLab is smooth and straightforward. There is no complexity as long as you're familiar with the basics. A simple code can be reused, facilitating easy installation and use.
What's my experience with pricing, setup cost, and licensing?
GitLab is mostly free, with potential costs arising from upgrade versions. There is a trial period of about six months during which it is free. Afterward, fees apply.
Which other solutions did I evaluate?
What other advice do I have?
I recommend GitLab for DevOps engineers. It is easy and fast to use. While Jenkins is also good for understanding, GitLab offers an easier user experience. I rate GitLab as ten on a scale of one to ten.
Helps to integrate CI/CD pipeline deployments and has good security model
What is our primary use case?
I use the tool for deployment.
What is most valuable?
The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good.
What needs improvement?
GitLab could consider introducing a code-scanning tool. Purchasing such tools from external markets can incur charges, which might not be favorable. Integrating these features into GitLab would streamline the pipeline and make it more convenient for users.
For how long have I used the solution?
I have been working with the product for six years.
What do I think about the stability of the solution?
I haven't encountered any bugs in GitLab.
What do I think about the scalability of the solution?
In our company, I estimate that around 30 people use GitLab, primarily for branching and repository management.
Which solution did I use previously and why did I switch?
Our organization decided to use GitLab because it's easy to use, and its user interface is more intuitive than other tools.
How was the initial setup?
The tool's deployment is easy.
What other advice do I have?
I would recommend using GitLab. It provides a repository and API, allowing you to create deployment pipelines. I rate it a ten out of ten.
Used for source code maintenance and provides user-friendly interface for code review and pull requests
What is our primary use case?
Our primary use case is for source code maintenance, then doing the build and running code coverage tools like SonarQube, and then deployment.
What is most valuable?
We have seen a couple of merge requests or pull requests raised in GitLab. I see the interface, the way it shows the difference between the two source codes, that it is easy for anyone to do the review and then accept the request; the pull request is the valuable feature.
What needs improvement?
We have only seen a couple of times on Gitlab, which we use for building some of the applications. Recently, we have heard that some of the builds were taking a long time or were not scheduled. In such cases, they had to contact the GitLab community or the GitLab organization to address these issues.
So, there is room for improvement in regard to the issues with build times.
In future releases, additional features could be added in post-deployment monitoring. Currently, GitLab supports CI/CD up to deployment. Anything that would assist in monitoring deployments, especially in the context of Kubernetes or Docker, would be valuable. It may not be necessary for enterprise-level use, but for midrange organizations, integrating post-deployment monitoring of infrastructures and generating reports could be beneficial.
For how long have I used the solution?
We have been using this solution for three years now.
What do I think about the stability of the solution?
The solution offers good stability. However, sometimes we do see some issues due to upgrades and patches. But a couple of times, we have seen build issues where it takes a long time, or it gets stuck, and people have to manually restart those.
What do I think about the scalability of the solution?
It is a scalable solution in our environment. We have over a thousand end users.
How are customer service and support?
The support is very good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Earlier, we were using Atlassian products, and then we shifted to GitLab.
What about the implementation team?
The deployment is handled by a different team. For maintenance, we get good support from GitLab. For any production issues, we hear that we get good support from GitLab. That is something good.
What other advice do I have?
My advice would be it's a very good tool for developers, especially those spread across the globe. It has a very good interface for any pull request or code review. The CI/CD pipeline is also easily built in, so we can easily build and deploy it into various environments. So that eases the developer's and the production ops team's life.
Overall, I would rate the solution a ten out of ten.
With great integration capabilities for small companies, the tool also provides a reasonable amount of stability
What is our primary use case?
My company's programmers use GitLab for everyday development purposes.
What is most valuable?
The solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people.
What needs improvement?
Some of the programmers in my company have had complaints about the product.
We do face issues in our company when we run out of disk space. We had to do some low-level system interventions to recover the server from GitLab in our company. It would be good if GitLab implemented some diagnostic features so that the server prevents functioning when it detects insufficient disk space. It is important to prevent cache to avoid running out of disk space. Considering the aforementioned details, making a recovery wasn’t simple.
For how long have I used the solution?
I have experience with GitLab.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
Owing to the small size of my company, we do not need to utilize the scalability feature of the product.
My company has around 20 users of the product.
How was the initial setup?
The initial setup of GitLab was okay.
The setup phase was completed in a day.
Our company has DevOps and CI/CD to help us with the deployment process of the product.
Though I am unsure, I feel that the solution is deployed on-premises.
What about the implementation team?
The deployment phase was carried out with the in-house members of our company.
What's my experience with pricing, setup cost, and licensing?
Speaking about the pricing of the solution, my company uses GitLab Community Edition.
Which other solutions did I evaluate?
Before choosing GitLab, my company had considered Microsoft TFS during the evaluation phase.
What other advice do I have?
GitLab is a product managed by the department of programmers in our company, and I am not much involved in it.
I recommend the solution to those planning to use it.
I rate the overall product a ten out of ten.
A feature-rich and a well-organized solution that is scalable
What is our primary use case?
It is used for saving source code, and then people get the source code out of it, make a branch, and merge it to make a big file for deployment. So it's mainly a source code deployment tool.
What is most valuable?
GitLab is very well-organized and easy to use. Also, it offers most features that customers need. So I think it's one of the best solutions compared to other options. So, it's the most capable and easiest tool.
What needs improvement?
In terms of the solution's interface and features, I am satisfied.
As a partner, sometimes it's difficult to get support. They have a really complicated procedure for their support. Apart from the aforementioned reason, I am very satisfied with the product. It is only after we are registered that we get proper support from GitLab. The registration itself it's quite complicated, and it is mainly because they want to make sure that the users with a license contact the right support team.
For how long have I used the solution?
I have been using GitLab for two years. My company has a partnership with GitLab. I am using GitLab Version 15.6.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution an eight or nine out of ten. Since it is software, they can have some bug-related issues, and no software is 100% protected. GitLab has many features in different areas, so I cannot specify which specific area has a problem.
What do I think about the scalability of the solution?
It is a scalable solution. Scalability-wise, I rate the solution a ten out of ten. My clients who use the solution are medium-sized businesses.
How are customer service and support?
The solution's technical support is good. I rate the technical support a ten out of ten. Only the initial registration is complicated.
How would you rate customer service and support?
Positive
How was the initial setup?
The solution's initial setup process was easy. I rate the initial setup a ten out of ten. The solution can be deployed in a day. Only one engineer is required to deploy the solution. Also, the solution does require maintenance. Using it as a different storage operation when it comes to maintenance, there can probably be some updates that can fix security patches and other issues. So, we have several employees working on many different solutions and projects. But only one person is actually required for its maintenance.
What's my experience with pricing, setup cost, and licensing?
Price-wise, it is a reasonable solution. On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a five out of ten.
What other advice do I have?
It's a great solution. So I would recommend it to those who want to use it. I rate the overall solution a ten out of ten.