Version Control for Complex Projects in Small-Mid-Size Companies
December 18, 2018
Version Control for Complex Projects in Small-Mid-Size Companies
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Gitlab
I've used Gitlab at multiple roles in a few different companies, though never as a lead developer or software engineer. Especially at a small to mid-size company, Gitlab's support for project management and version control using git repos can't be beat. It works as a platform to allow for cross-organizational collaboration on code repositories. A major reason to use Gitlab in an organization is its CI/CD (continuous integration/continuous deployment) pipeline, which facilitates the passing of code to the repos reliably and quickly between team members.
- CI/CD capabilities.
- Variable access/security levels for different users within an organization or working on a project.
- Project management capabilities far surpass GitHub's PM capabilities: easier to manage and organize contributions to repos.
- Interface and use can be overwhelming for new users: built-in tutorial or key highlights would be helpful to lessen the learning curve.
- Project management has improved deployment, communication, and productivity by keeping everyone on the same page.
- Highly customizable with continuous integration, which means there's no need to connect multiple services together to achieve the desired result.
- Easy to setup and work on multiple projects simultaneously.
While they're separate services, both Gitlab and GitHub work as git repositories (version control) for collaborative, shareable work. They offer similar functionality, but with Gitlab, there's a continuous integration/continuous deployment (CI/CD) pipeline and project management tools. Gitlab is more suited to working concurrently on multiple projects in a small to mid-size company, especially when individuals with different security levels will be contributing / pulling code.