Gitlab much more than a software version control system
September 01, 2025
Gitlab much more than a software version control system
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with GitLab
We used Gitlab on-premise as a corporate repository for all the software developed in the organization. We also used its continuous integration capabilities to manage deployments to development and production environments in a controlled manner. The development and systems teams coordinated their use of this solution.
Pros
- It's a very powerful software version control system with extensive capabilities
- It allows for comprehensive project management, including project control and planning, and task allocation to the team
- It has extensive integration capabilities with other systems
Cons
- Learning curve to take advantage of all the included features
- Software updates in on-premise environments are not a problem in the cloud
- Configuring certain on-premise features via files
- Software project management was transferred to Gitlab, with agile management that allowed bottlenecks and delivery delays to be detected early.
- Continuous integration enabled deployment to basically any scenario; in our case, integration with Docker was essential.
- It allows integration with virtually any existing development environment, which is an advantage in corporations where heterogeneous software is developed.
In our case, we opted for an open source solution and complete control of information, meaning we kept critical information and company developments in-house.
We only use the open source version on-premises.However, I believe the cloud platform is an excellent solution for companies that don't want to be complicated by maintenance and updates and also want easy access to new features and security patches.
Once the workflow is established, Gitlab is essential for the development team; it's an integral part of the team.However, it's necessary to have a solid understanding of how the team uses the tool and to be clear about internal procedures for using it. This includes issues such as when to publish a branch, where, how to name it, how to inform the team, etc.
Do you think GitLab delivers good value for the price?
Yes
Are you happy with GitLab's feature set?
Yes
Did GitLab live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of GitLab go as expected?
Yes
Would you buy GitLab again?
Yes
Comments
Please log in to join the conversation