The best chemistry of version control happens in Gitlab
Overall Satisfaction with Gitlab
We use Gitlab across our entire business, from documentation to code versioning to CI/CD and IaaS. We've used other documentation tools such as Confluence by Atlassian but we keep coming back to Markdown in Gitlab because of the simplicity, exportability, portability, better versioning, better integration - such as with Readthedocs. Our helpdesk team finds Gitlab easy to use. We also use Gitlab for our development teams and operations teams.
Pros
- Markdown.
- CI/CD integration.
- User and group management.
- Branding.
- Standard Gitlab implementation.
Cons
- Themes.
- Need to reconfigure too often.
- Use the same Markdown engine everywhere.
- Better documentation.
- Better bug fixes.
- Better team coordination.
- Better productivity from our operations and development teams.
Gitlab surpasses Bitbucket in all areas except of course the very tight integration Bitbucket has with JIRA and Confluence. Almost everyone uses JIRA at some level or time so Bitbucket has a more natural and tight integration feel. However, there is good JIRA integration with Gitlab and we have found that we're not sacrificing anything to afford ourselves a better experience in every other area when choosing Gitlab over Bitbucket.
Gitlab is as good as GitHub in every area that we use version control. It excels in that we keep everything in-house and tightly monitored. We do not open our Gitlab instances to anonymous users and our public repositories are public only to our teams.
Gitlab is as good as GitHub in every area that we use version control. It excels in that we keep everything in-house and tightly monitored. We do not open our Gitlab instances to anonymous users and our public repositories are public only to our teams.
Comments
Please log in to join the conversation