GitLab, all in one for source code

Item: GitLab
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

We use GitLab to manage the source code of all applications. It replaced an old CVS. We needed a more modern tool with greater integration for developers. We also needed a fully integrated tool for code reviews and issues management. For two years, GitLab replaced Jenkins for building pipelines and ci/cd.

Pros and Cons

Git integration
Pipelines
Merge request

Pipelines visualization
Diff with many files

Return on Investment

Easy access to code
Issues management

Alternatives Considered

I was not part of the decision for GitLab.

Security

I did not use GitLab security features.

Continuous Integration

Codesharing in GitLab helps us every day to resolve production issues. It's also very easy to conduct code reviews with merge requests and issues. Continuous integration in the same tool makes it easy to see all applications' life on the same interface.

Key Insights

Do you think GitLab delivers good value for the price?

Not sure

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

Jenkins, SonarQube, Eclipse, Docker

Likelihood to Recommend

GitLab is a great tool in Enterprise for git integration with a simple but efficient user interface. It's fluid and helpful with, for example, the branch graph. I regret only one feature from Jenkins where we could easily see on a build which version we actually built. In GitLab ci, we cannot have this information directly on the screen.