What I love about GitHub

Item: GitLab
Rating: 8
Author: Chukwuma Esoga

Overall Satisfaction with GitLab

Use Cases and Deployment Scope

We use GitLab across multiple departments as a code repository. Currently, my team uses it to store and manage our code repository as well as create builds and versioning with it.

Pros and Cons

Pros

Code Storage.
Manages roles around identities so makes it easy to grant access based on users.
Allows us create multiple builds.

Cons

Would love to see some CI and CD functionality.
More Streamlined and fine grained Permissions management.

Return on Investment

We have seen increased code management since we started using GitLab even for non-development efforts.

Alternatives Considered

Azure DevOps Services (formerly VSTS) and GitHub

Continuous Integration

This feature is currently not enabled in our environment.

Key Insights

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?

I wasn't involved with the implementation phase

Would you buy GitLab again?

Yes

Other Software Used

SailPoint Identity Platform, Azure DevOps Services (formerly VSTS), Microsoft Azure Active Directory

I particularly like the fact that I can store my code in GitLab and be able to grant multiple users access to it with specific restrictions. For instance in my environment, we have C- level executives that would like to review the codes before a build is done, I can grant access to view the code but am not able to make changes. They can leave their comments but that won't be able to affect the actual codebase whereas I can grant the developer role to my colleagues who will be able to make those changes and save it using versioning.

Comments

Please log in to join the conversation