Overall Satisfaction with Gitlab
We use it for nearly all of our projects, as one of the central repository and DevOps tools. We use most of its features, mostly the repository, ticketing, and CI/CD pipelines. It has been our main project management tool for many years now.
- Very nice and high UX value GUI.
- Pipeline administration.
- Issue tracking and wiki functionality.
- Must restart it when we upgrade it, upgrade processes tend to be problematic.
- We can use GitLab instead of multiple different tools.
- We changed our deployments scripts to GitLab pipelines which provided to be more maintainable.
- Issue-tracking is much faster with its simple UI.
GitLab is the best combination of all the other tools. They are still viable in their own sense, but for the projects we were using, GitLab proved to be an excellent alternative.
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
Collaboration and Performance
It made collaboration incredibly easier! Gitlab serves as the central nerve for nearly all of our projects, where we store code, documentation, configuration for every project of the entire company. Accessing and working on code and documents at the same time, from the office or from home, Gitlab is one of the best collaboration tools, and it's main power is in collecting all the different features of a softwer writing process to the same place.
Gitlab itself has some support on applying best practices, but it only serves as a base for that. It's gitlab ci system allows us to create jobs and workflows, which is quite easy to learn and easy to maintain. It serves as an excellent foundation for the said techniques, but it's not a guarantee.
Yep, it has replaced nearly all of our tools.
- Our documentation has moved from JIRA to Gitlab Wiki
- Our CI and release manager is now Gitlab instead of Jenkins
- We changed our custom VM system to Gitlab workers
- Our kanban boards and ticketing systems are now all merged into Gitlab as well.
- Our documentation has moved from JIRA to Gitlab Wiki
- Our CI and release manager is now Gitlab instead of Jenkins
- We changed our custom VM system to Gitlab workers
- Our kanban boards and ticketing systems are now all merged into Gitlab as well.