Overall Satisfaction with GitLab
We are using GitLab as a common internal platform.
It is used by several departments across the whole organization (IT Department, DevOps team, Services, etc.).
GitLab is used for several reasons:
It is used by several departments across the whole organization (IT Department, DevOps team, Services, etc.).
GitLab is used for several reasons:
- Versioning server (it stores all company's sources code).
- Task and issue boards.
- Wiki (it stores all useful information related to projects).
- Continuous Integration and Continuous Delivery.
- Linked to external tool as SonarQube (Code Analysis / Security).
- Issue / task board.
- CI/CD.
- Code Review.
- Wiki.
- Reports.
- Reduce time to deploy.
- Easier rollback.
- Better code review.
- Increase efficiency.
- Azure DevOps Server (formerly Team Foundation Server)
GitLab can be installed OnPrem, and in my company, we had to choose a solution that was not on the Cloud.
Compare to GitLab, this solution consumed more resources and performance. (Same for server costs.)
- Open source.
- Several security / fix updates per month.
- New release every month.
Compare to GitLab, this solution consumed more resources and performance. (Same for server costs.)
We are not using any of GitLab's paid plans.
We are using GitLab CI/CD tools on a daily basis. It is used to deploy our developments to all of our platforms: staging, quality, production.
CI/CD is used for several reasons :
CI/CD is used for several reasons :
- Deployments.
- Build.
- Unit test.
- Security/Analysis tests (with additional tool SonarQube).
- Documentation analysis.
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?
Yes
Did implementation of GitLab go as expected?
Yes
Would you buy GitLab again?
Yes