We use the solution as a source code manager or version control manager.
GitLab Ultimate
GitLabExternal reviews
External reviews are not included in the AWS star rating for the product.
Works as a source code manager or version control manager
What is our primary use case?
What is most valuable?
In our software development lifecycle, GitLab is used as a component for code repository management. We use GitLab for several projects to handle code repositories. For other software projects, we use Bitbucket, but the use case for both is very similar.
Many global users prefer GitLab for its enhanced pipeline automation for CI/CD features. It stands out among source code managers due to its parent-child pipeline feature. If users want to leverage this feature, they should consider using it. It’s not the only platform with this capability, but GitLab excels in automating many operations and offers integration with other platforms.
The solution supports platforms like Azure, GCP, and AWS. This capability makes it a preferred choice, even though other platforms also offer similar integration features. Additionally, GitLab’s tendency to be independent of ownership by another major company makes it an attractive option for many developers who prefer cloud usage
The tool's UI is good.
What needs improvement?
In the next release, I would like to see GitLab expand its integration capabilities to include platforms like DigitalOcean, which developers widely use for cloud infrastructure. Enhancing CI/CD automation features specifically tailored for DigitalOcean would be beneficial.
For how long have I used the solution?
I have been working with the product for more than six months.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The product is scalable.
How are customer service and support?
The tool's technical support is great.
What's my experience with pricing, setup cost, and licensing?
The solution is free.
What other advice do I have?
I rate the overall product an eight out of ten.
Useful for source code management and security purposes
What is our primary use case?
When a developer checks in code, it is automatically built and deployed, and automated test cases are also run. We have extensive integration with GitLab, which helps us with source code management. We run the static code analysis using SonarQube.
What needs improvement?
Technologies are always changing. Nowadays, new things like serverless computing and workload management have emerged. We have noticed a few gap items for faster service delivery. For example, we do user interface testing in the latest team and automate it using some tools. Recently, we integrated a tool with user interface testing, which can simulate a multi-user environment. So, we would like to see more integration with different platforms.
What do I think about the stability of the solution?
We normally do load testing for an hour, extending that load with two or three different use cases. We increase the load by two or three times to check how the application responds. This helps us see if the application can withstand increased load, though it may reject messages or requests when it can't handle two to three times the normal load.
We do endurance or soak testing by leaving the system at the rated load, like 300 requests per second, for 12-16 hours to observe stability. We monitor for CPU leakage, memory leakage, queue building, and similar issues. If there are any problems, we fine-tune and fix them. For performance testing, we test at multiple levels: one at the service level and two at the system level. We normally don't test at the integration level.
What do I think about the scalability of the solution?
My company has 90 users.
How was the initial setup?
The solution's deployment is straightforward. We have containerized applications that are deployed to the environment.
What about the implementation team?
GitLab was deployed in-house.
What was our ROI?
The main value and impact of using the product are significant. We create and maintain vulnerability-free software by integrating tools like ManageEngine, which periodically patches our runtime environments, including operating systems, kernels, and software. Additionally, we run automated Nessus scans periodically, every week and day, to identify new vulnerabilities even after applying patches.
What other advice do I have?
I rate the overall solution an eight out of ten.
We do two levels of security scanning. One is at the build level, where we integrate with security packages and use tools like OWASP for top vulnerability compliance. This ensures that all third-party tools, like Tomcat and JBoss, are scanned as part of the build.
The second level is a reactive scan at runtime. We scan Oracle clients, JDKs, JBoss, Tomcat, Log4j, and other components during runtime. We also consider the operating system's security. Before we complete software testing, we use Nessus to perform a runtime security scan.
Outstanding tool for version control
De-facto standard for Code Repository
Gitlab: Manage your codebase
It provides a single platform to manage, configure, and use your tech codebase, and infrastructure.
Gitlab- a web based project management repository
Alongside, this is also a reliable way to process, maintain and manage the code with minimum extra effort.
It's accuracy is another added advantage
Great Source Control Tool!
Amazing all in one DevSecOps platform
Good alternative to github!
Version control history is valuable for our development workflow
What is our primary use case?
We create the pipeline and push it to GitLab to initiate the process. The cloud integration is straightforward.
How has it helped my organization?
When it comes to GitLab's CI/CD integration, it significantly supports our development process by accelerating deployments. With automated pipelines, we can focus more on development tasks without worrying about manual deployments, ultimately speeding up our development cycle.
What is most valuable?
In GitLab, I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently. I haven't utilized GitLab's security scanning capabilities yet.
We plan to integrate tools like Sonicheap for code security. Currently, we use another product for security, focusing on Q4 security points.
We have used GitLab's features selectively for added security. We don't store passwords directly but use a secret manager and tools to sync passwords securely to our deployment environment.
What needs improvement?
I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities. Better integration and usability within the pipeline could make a significant difference in user experience. I would suggest considering new features or functions that could streamline workflows further and make using GitLab even more efficient. Having additional functionalities that cater to specific needs could greatly enhance the overall experience with the platform.
For how long have I used the solution?
I have been working with GitLab for the past 5 years.
What do I think about the stability of the solution?
Regarding stability, while I can't rate it on a scale of one to ten, I can say that we've experienced good stability with GitLab, with no downtime or major issues.
What do I think about the scalability of the solution?
How are customer service and support?
I've had support from forums like Stack Overflow when needed. In my experience, GitLab integrates well with third-party tools like SonicWall and Slack without any major issues.
How was the initial setup?
The setup process for GitLab is straightforward and easy to use.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, I would rate GitLab as moderately priced, maybe around a seven or eight out of ten. It could be more flexible for clients but generally offers good value.
Which other solutions did I evaluate?
When comparing GitLab to competitors like Bitbucket, I find GitLab to be superior, especially in terms of features and functionality. Bitbucket still has its own strengths and is preferred by some organizations.
What other advice do I have?
Overall, I would rate GitLab around eight or nine out of ten. I highly recommend it to other users for both company purposes and personal projects. GitLab provides a solid starting point for learning and working efficiently, making it a valuable tool for developers.