Best Choice For Software Development Lifecycle Management
Updated October 11, 2022

Best Choice For Software Development Lifecycle Management

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with GitLab

We are using GitLad for the version control of multiple projects. It helps us to allow managing the delivery of multiple versions of a product by using in-build pipelines. In addition, code quality control is also done using GitLad by implementing quality gates alongside of merge requests and by peer review in the merge requests. My personal experience has been very good with GitLad as I use the features like cherry-picking commits from one versions of the product into some other version of the same product.
  • Version control
  • Merge request (changes) management by allowing review
  • Quality control
  • Docker integration
  • Git GUI is very helpful
  • Better management of merge requests having large amount of code changes
  • Increase in code quality
  • Better management of product KPI (Key Performance Indicator)
Apache Subversion is an old version control but GitLab is far better now. GitLab provides a better UI and integration of other applications such as docker, sonar etc. which helps in the better management of the project in terms of code quality, integration, code changes merge etc.
We are using other plugins for the security management.
Team members can easily push their code changes and raise a merge request to merge their code changes. Later, these code changes can be reviewed by teammates by using the GitLab UI which is an excellent way of identifying the code changes done in the merge request. It is very helpful for the developers to review, approve and then merge the code changes using the merge requests.

Do you think GitLab delivers good value for the price?


Are you happy with GitLab's feature set?


Did GitLab live up to sales and marketing promises?


Did implementation of GitLab go as expected?


Would you buy GitLab again?


Atlassian JIRA Align (formerly AgileCraft), Eclipse, Notepad++
GitLab is best suited when you have to manage multiple versions of a project. For e.g., you can have 1.x.x and 1.x.y versions of a project. It allows you to manage these 2 versions very comfortably. Also, when you want to manage code quality, peer-reviews etc. all in single place then GitLab is highly recommended to use.

Collaboration and Performance

Collaboration is easier when using Gitlab. Developers can push the code changes in the feature branch by adding commits. Those code changes can be reviewed using the Changes tab of the merge request. Developers can put the comments when doing the peer code review. Then those comments can be resolved by adding new commits. That's how collaboration is easy when using Gitlab because it provides all the necessary features which enriches the user experience.
We are using Gitlab for the peer code review. We have added a template in the Gitlab which is required to be followed during the code review phase. It is easy to review the code when referring to the template. Also, we have added Sonar Qube in the pipeline stages so most of the code related issues are already captured in the Sonar Qube report. Thanks to the Giltab for easy integration of such plugins.
We have replaced Jenkins with the CI/CD deployment which is provided by Gitlab and it has helped in achieving the automation of deployment for our project. Also, previously we were using SVN but now Gitlab is used even for storing and maintaining versions of Customer documents for example Release Notes, Technical Documents, etc.